svn commit: r1553085 - /commons/cms-site/trunk/content/xdoc/releases/prepare.xml

[britter]

Author: britter
Date: Mon Dec 23 09:18:53 2013
New Revision: 1553085

URL: http://svn.apache.org/r1553085
Log:
Describe how to set the correct value for the Build-By MANIFEST header

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=1553085&r1=1553084&r2=1553085&view=diff
==============================================================================
--- commons/cms-site/trunk/content/xdoc/releases/prepare.xml (original)
+++ commons/cms-site/trunk/content/xdoc/releases/prepare.xml Mon Dec 23 
09:18:53 2013
@@ -202,7 +202,7 @@
            entries set to the correct values. </li>
       <li> The jar manifests include correctly set OSGi bundle properties (ask 
for help verifying these on
            commons-dev if necessary). </li>
-      <li> The jar manifests include the following required properties, set to 
the correct values:
+      <li> The jar manifests include the following required properties, set to 
the correct values(*):
       <pre>
   Extension-Name: org.apache.commons.foo
   Specification-Title: Apache Commons Foo
@@ -211,13 +211,17 @@
   Implementation-Vendor-Id: org.apache
   Implementation-Title: org.apache.commons.foo
   Implementation-Vendor: The Apache Software Foundation
-  Implementation-Version: 1.2 </pre></li>
+  Implementation-Version: 1.2 
+  Built-By: &lt;your apache ID&gt;</pre></li>
       <li> "mvn site" generates the documentation correctly and all links are 
working.</li>
       </ol>
       Do not proceed with tagging or cutting RCs until you have a fully 
working build that produces
       a good set of distribution artifacts.  If your component supports both 
Ant and Maven builds, make
       sure that the build succeeds using both on all supported JDK versions.  
If you have access to
-      multiple platforms, test the build(s) on as many as you can. 
+      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=&lt;your apache ID&gt;</code> to change this.
       </p>
     </subsection>
   </section>
@@ -526,6 +530,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=&lt;your apache ID&gt;</code> to 
make sure the <code>Build-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>