Author: bodewig Date: Mon Oct 6 04:04:17 2014 New Revision: 1629565 URL: http://svn.apache.org/r1629565 Log: fix typo in MANIFEST attribute name
Modified: commons/cms-site/trunk/content/xdoc/releases/prepare.xml Modified: commons/cms-site/trunk/content/xdoc/releases/prepare.xml URL: http://svn.apache.org/viewvc/commons/cms-site/trunk/content/xdoc/releases/prepare.xml?rev=1629565&r1=1629564&r2=1629565&view=diff ============================================================================== --- commons/cms-site/trunk/content/xdoc/releases/prepare.xml (original) +++ commons/cms-site/trunk/content/xdoc/releases/prepare.xml Mon Oct 6 04:04:17 2014 @@ -224,7 +224,7 @@ multiple platforms, test the build(s) on as many as you can. </p> <p> - (*) The default configuration of the build will use the name of the current logged in user as value for the <code>Build-By</code> MANIFEST header. Use <code>-Duser.name=<your apache ID></code> to change this. + (*) The default configuration of the build will use the name of the current logged in user as value for the <code>Built-By</code> MANIFEST header. Use <code>-Duser.name=<your apache ID></code> to change this. </p> </subsection> </section> @@ -533,7 +533,7 @@ The "test-deploy" profile uploads the artifacts to target/deploy instead of Nexus so one can check all the required files have been created with the expected contents. Best to run "mvn clean" before doing the live deployment. - Again remember to use <code>-Duser.name=<your apache ID></code> to make sure the <code>Build-By</code> MANIFEST header is correct. + Again remember to use <code>-Duser.name=<your apache ID></code> to make sure the <code>Built-By</code> MANIFEST header is correct. </p> <p>This will PGP-sign all artifacts and upload them to a new staging repository, Nexus itself will create MD5 and SHA1 checksums for all files that have been uploaded.</p>