Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Add a background section about preventing lost license headers (from POMs)

DRAFT Procedure for creating a release using M2

'This is currently a discussion page, and is not (yet) policy

Background

Wiki Markup
See Maven documentation: \[http://maven.apache.org/developers/release/releasing.html Releasing A Maven Project\].

Please prepare the POM(s) for the release, quoting from the above page:

Check that your poms will not lose content when they are rewritten during the release process.

  • mvn release:prepare -DdryRun=true
  • Diff the original file pom.xml with the one called pom.xml.tag to see if the license or any other info has been removed. This has been known to happen if the starting <project> tag is not on a single line. The only things that should be different between these files are the <version> and <scm> elements. Any other changes, you must backport yourself to the original pom.xml file and commit before proceeding with the release.
  • Remember to do 'mvn release:clean ' before you start the real release process.

Procedure for creating a release using M2

This assumes that the Commons Proxy is about to vote on 1.0-RC3.

...