You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The key assets conflicts with the key, assets, in the SBT plugin for Play framework.
So when both are put in the plugins.sbt file and either or both are used in the build.sbt or Build.scala, it causes the following exception.
Some keys were defined with the same name but different types: 'assets' (sbt.Task[java.io.File], sbt.Task[scala.collection.Seq[java.io.File]])
Play framework is such a popular framework so I think it is better to avoid that conflict then doing any extra work to avoid it when using it. And I'm not sure if there is any easy workaround for this.
I've changed the assets to releaseAssets in my forked repo of sbt-github-release and will deploy it to my Bintray repo to test it properly. If it works well, I'll create a pull request. So please consider my suggestion.
The text was updated successfully, but these errors were encountered:
kevin-lee
added a commit
to kevin-lee/sbt-github-release
that referenced
this issue
Jun 4, 2015
- Fixed key name conflict with Play plugin's (#4/#5 by @kevin-lee)
```
Some keys were defined with the same name but different types: 'assets' (sbt.Task[java.io.File], sbt.Task[scala.collection.Seq[java.io.File]])
```
`assets` key is renamed to `releaseAssets`
The key
assets
conflicts with the key,assets
, in the SBT plugin for Play framework.So when both are put in the
plugins.sbt
file and either or both are used in thebuild.sbt
orBuild.scala
, it causes the following exception.Play framework is such a popular framework so I think it is better to avoid that conflict then doing any extra work to avoid it when using it. And I'm not sure if there is any easy workaround for this.
I've changed the
assets
toreleaseAssets
in my forked repo ofsbt-github-release
and will deploy it to my Bintray repo to test it properly. If it works well, I'll create a pull request. So please consider my suggestion.The text was updated successfully, but these errors were encountered: