|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
I'd like to make the jenkins-dev prefix available without further configuration, as suggested in the issue.
maven-jenkins-dev-plugin explicitely declares hudson-dev as its goalPrefix.
My understanding of http://maven.apache.org/guides/introduction/introduction-to-plugin-prefix-mapping.html is that this setting makes the default prefix jenkins-dev (derived from the artifactId), unavailable to default plugin resolution.
Thus, removing the goalPrefix declaration should make jenkins-dev available.
But this is my first contact with maven plugin programming, so any advice is welcome.