Versions Compared

Old Version 13

changes.mady.by.user Stefano lenzi

Saved on

compared with

New Version 14

changes.mady.by.user Unknown User (fmeschbe)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Add note about password encryption support in Maven 2.1 and later

...

  • each and every release must be SIGNED; your public key should be added to http://www.apache.org/dist/felix/KEYS (see Appendix A)
  • your public key should also be cross-signed by other Apache committers (not required, but suggested)
  • when preparing the release on Mac OS X, make sure you read Appendix B before continuing
  • make sure you have all Apache servers defined in your settings.xml

Note: Listing the Apache servers in the settings.xml file also requires adding the password to that file. Starting with Maven 2.1 this password may be encrypted and needs not be give in plaintext. Please refer to Password Encryption for more information.

In the past we staged release candidates on our local machines using a semi-manual process. Now that we inherit from the Apache parent POM version 5, a repository manager will automatically handle staging for you. This means you now only need to specify your GPG passphrase in the release profile of your ${user.home}/.m2/settings.xml:

...