-
Notifications
You must be signed in to change notification settings - Fork 17
repo name / plugin name #23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
I totally agree! |
I don't mean to feature creep this ticket (but I also don't feel strongly enough to create a new one), but with regards to the plugin best practices there's also the one about key namespace clashes: http://www.scala-sbt.org/0.13/docs/Plugins-Best-Practices.html#Avoid+namespace+clashes. |
I have renamed the repository. keeping the issue open until I actually publish 1.0.9, which I'll do shortly |
I now thiiiiiiink I did everything right, but the final step, where I added my repo to https://bintray.com/sbt/sbt-plugin-releases, has to be approved by @eed3si9n, apparently |
it bugs me that the repo is named
sbt-scala-modules
but the plugin is published asscala-module-plugin
. as a result I have trouble remembering both namesI suggest we:
sbt-scala-module
, singularsbt-scala-module
as well (as per http://www.scala-sbt.org/0.13/docs/Plugins-Best-Practices.html)objections?
The text was updated successfully, but these errors were encountered: