Looks like the error message is pretty self-explanatory.
Plugin IDs may only contain ASCII alphanumerics, ‘.’ and ‘-’
I’d probably just replace the underscore with a hyphen and call it a day. That being said, the instructions for publishing a plugin, located here should probably be updated to reflect this.
No, there are still limitations. However, they are sync’d between the two systems. So you can’t have a plugin in the portal that violates the constraints.
It is a common practice to publish scala libraries maven artifacts followed by the scala major version used. This is a very specific purpose plugin that generates scala code.
I managed to maintain a single code base to publish this plugin for scala 2.10 and 2.11. But compared to sbt, gradle support for cross scala compilation is still in it’s first steps to allow me to strip the scala version part of this plugin ID.