On Tue, Jan 19, 2016 at 6:27 AM, <[email protected]> wrote: > Decide the final artifact maven coordinates: following the criteria used in > jenkins-test-harness, we could keep the same groupId / artifactId than > before and bump version to 2.0.
Yes I think making it be `org.jenkins-ci.plugins:plugin:pom:2.0` would be appropriate. If nothing else, this advertises it as an upgrade for people who use standard Maven tools or IDEs to look for new versions of artifacts (in this case parent POM). Of course you need to make certain changes to your plugin’s POM to use it (in most cases you would want to define `jenkins.version` at a minimum), but that seems OK—the bump in major version should be sufficient indication that something noteworthy has changed. > Create a repository in the jenkinsci GitHub org (by someone with permissions > forking the existing one). I can do this if there are no objections. The main question is the repository name. `plugin-pom`? > Perform a release. And I suggest that `jenkinsci/jenkins/plugins/pom.xml` be deleted. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr0A6jrobt2phksSqC9cE_qh%3D56wEnhOmurhFerj5DgRmA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
