-
Notifications
You must be signed in to change notification settings - Fork 113
Add support for auto plugins in sbt 0.13.5 #51
Comments
Can you explain more which kind of behavior you are missing that would be enabled by supporting an auto-plugin style? |
I have this plugin being configured in a corporate level plugin and thus the configuration is inherited by every project. I would be really nice to have this in the corporate plugin but be able to disable in this as needed in a select few projects that we still want to use the corporate plugin but the dependency-graph plugin has some issues or conflicts. I am not sure what the issues are as they are not my projects. It would make using the plugin much easier as well as all I would have to do something like this: def myCompanytProject(projectName: String): Project = ( Then, a project that wants to turn it off can simply do this: myCompanyProject(“foo”) This is one of the use cases it was defined for and something that we are heavily using already with all of the Play,SbtWeb and Typesafe plugins that have updated already. On Jul 7, 2014, at 1:06 AM, Johannes Rudolph notifications@github.com wrote:
|
Thanks for the explanation. I agree that this would be useful. |
I'd also appreciate having this as an autoPlugin. That way one can have in in the sbt global plugins and have the settings automatically merged without changing shared build files. If it's an effort thing, would you be open to a PR containing the conversion? |
I could make a pull request, but I'm not familiar with the sbt-crosscompile stuff and how to handle this. How important is the backwards compatibility with sbt |
Thanks @muuki88 for the offer. I'm just wrapping up a new version which also has autoplugin support which I hope to have ready soon. So, don't bother with a PR this time. |
Okay :) Looking forward to it |
Fixed in adc55e3. |
Add support for auto plugins in sbt 0.13.5
The text was updated successfully, but these errors were encountered: