MavenNbmPluginAndArchetypesReleaseGuide

(Difference between revisions)
(Releasing maven-nbm-plugin)
Line 9: Line 9:
# Prepare release for real, don't forget SCM credentials: '''mvn -Dusername=<scm_username> -Dpassword=<scmpassword> release:prepare'''
# Prepare release for real, don't forget SCM credentials: '''mvn -Dusername=<scm_username> -Dpassword=<scmpassword> release:prepare'''
# Perform release using '''mvn release:perform'''. This can take several tens of minutes, especially when run for the first time.
# Perform release using '''mvn release:perform'''. This can take several tens of minutes, especially when run for the first time.
 +
 +
Note that you can run into problems in SCM tagging step - see http://jira.codehaus.org/browse/MRELEASE-353 for workaround.
==Releasing archetypes==
==Releasing archetypes==
The same steps above applies, pick archetypes that needs to be released and release one by one. Pay attention to follow the naming for SCM tags and versions.
The same steps above applies, pick archetypes that needs to be released and release one by one. Pay attention to follow the naming for SCM tags and versions.

Revision as of 10:35, 9 April 2010

Note that committer access to http://xircles.codehaus.org/projects/mojo is needed for releasing new version of maven-nbm-plugin and archetypes. Be sure to read and follow codehaus standards and development process, see http://mojo.codehaus.org/.

Releasing maven-nbm-plugin

  1. Read documentation of Maven release plugin carefully: http://maven.apache.org/plugins/maven-release-plugin/index.html
  2. Commit all source changes, build and test.
  3. Do dry run of release:prepare. In root folder of nbm plugin project type: mvn release:prepare -DdryRun=true. Answer questions and respect the notation, typical pattern would be: X.Y for version being released, nbm-maven-plugin-X.Y for SCM tag and X.Y+1-SNAPSHOT for next development version.
  4. Review generated xmls in root project's folder, then clean to prepare for full release: mvn release:clean
  5. Prepare release for real, don't forget SCM credentials: mvn -Dusername=<scm_username> -Dpassword=<scmpassword> release:prepare
  6. Perform release using mvn release:perform. This can take several tens of minutes, especially when run for the first time.

Note that you can run into problems in SCM tagging step - see http://jira.codehaus.org/browse/MRELEASE-353 for workaround.

Releasing archetypes

The same steps above applies, pick archetypes that needs to be released and release one by one. Pay attention to follow the naming for SCM tags and versions.

Not logged in. Log in, Register

By use of this website, you agree to the NetBeans Policies and Terms of Use. © 2012, Oracle Corporation and/or its affiliates. Sponsored by Oracle logo