Author: buildbot
Date: Sat Jan 10 23:06:49 2015
New Revision: 935752

Log:
Staging update by buildbot for commons

Modified:
    websites/staging/commons/trunk/content/   (props changed)
    websites/staging/commons/trunk/content/commons-parent-pom.html

Propchange: websites/staging/commons/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Sat Jan 10 23:06:49 2015
@@ -1 +1 @@
-1650771
+1650825

Modified: websites/staging/commons/trunk/content/commons-parent-pom.html
==============================================================================
--- websites/staging/commons/trunk/content/commons-parent-pom.html (original)
+++ websites/staging/commons/trunk/content/commons-parent-pom.html Sat Jan 10 
23:06:49 2015
@@ -327,6 +327,12 @@
             <b><a href="#Java_Version">Java Version</a></b> - <tt>source</tt> 
and <tt>target</tt>
             options can be configured through <i>properties</i> and 
<i>profiles</i> are provided to test on
             different Java versions.
+            Where necessary, plugins are down-graded to the latest version 
that runs on earlier JVMs.
+          </li>
+          
+<li>
+            <b><a href="#Testing_Coverage">Testing Coverage</a></b> - both 
<tt>Jacoco</tt> and <tt>Cobertura</tt>
+            are supported. These can be independently enabled.
           </li>
         </ul>
       </div>
@@ -338,7 +344,7 @@
 <p>
           The following is a list of the main <i>release</i> features provided 
by
           <a class="externalLink" 
href="http://svn.apache.org/repos/asf/commons/proper/commons-parent/trunk/pom.xml";>commons-parent</a>
-          through the <a href="#rc_profile">rc</a> and <a 
href="#release_profile">release</a> profiles.
+          through the <a href="#release_profile">release</a> profile.
         </p>
         
 <ul>
@@ -420,6 +426,37 @@
 <li><b>Javadocs</b></li>
               
 <li><b>Source Cross Reference</b></li>
+              The pom excludes Maven defaults such as the <tt>license</tt> 
report which is against the ASF branding rules.
+              The following are currently included by default (components can 
add extra ones if they wish, but cannot remove them).
+              
+<ul>
+                
+<li><tt>index</tt></li>
+                
+<li><tt>summary</tt></li>
+                
+<li><tt>modules</tt></li>
+                
+<li><tt>project-team</tt></li>
+                
+<li><tt>scm</tt></li>
+                
+<li><tt>issue-tracking</tt></li>
+                
+<li><tt>mailing-list</tt></li>
+                
+<li><tt>dependency-info</tt></li>
+                
+<li><tt>dependency-management</tt></li>
+                
+<li><tt>dependencies</tt></li>
+                
+<li><tt>dependency-convergence</tt></li>
+                
+<li><tt>cim</tt></li>
+                
+<li><tt>distribution-management</tt></li>
+              </ul>
             </ul>
           </li>
           
@@ -716,39 +753,27 @@
 
       
 <div class="section">
-<h3><a name="rc_profile"></a>rc profile</h3>
+<h3><a name="jacoco_profile"></a>jacoco profile</h3>
         
 <p>
-          <a class="externalLink" 
href="http://svn.apache.org/repos/asf/commons/proper/commons-parent/trunk/pom.xml";>commons-parent</a>
-          contains an <tt>rc</tt> profile for producing <i>release 
candidates</i>.
+        Enable this profile to run the Jacoco tool.
+        This requires at least Java 1.5.
+        The profile is not enabled by default.
+        If the file <tt>src/site/resources/profile.jacoco</tt> exists then the 
profile is enabled.
+        This allows components to always enable the profile
         </p>
+      </div>
 
+      
+<div class="section">
+<h3><a name="covertura_profile"></a>covertura profile</h3>
         
 <p>
-          Running the following command will, in addition to creating the jar 
as normal, will also:
-        </p>
-        
-<ul>
-          
-<li>produce the source and binary distributions</li>
-          
-<li>produce the javadoc and sources jars</li>
-        </ul>
-
-        
-<div class="source">
-<pre>mvn -Prc package</pre></div>
-
-        
-<p>
-          Running the following command will, as well as doing producing 
everything specified above for
-          the <i>package</i> command, also sign the artifacts and create 
checksums (in local m2 repo):
+        Enable this profile to run the Cobertura tool.
+        The profile is not enabled by default.
+        If the file <tt>src/site/resources/profile.cobertura</tt> exists then 
the profile is enabled.
+        This allows components to always enable the profile
         </p>
-
-        
-<div class="source">
-<pre>mvn -Prc install</pre></div>
-
       </div>
 
       
@@ -824,44 +849,50 @@
 
       
 <div class="section">
-<h3><a name="trunks-sandbox_profile"></a>trunks-sandbox profile</h3>
+<h3><a name="release-notes_profile"></a>release-notes profile</h3>
         
 <p>
-          <a class="externalLink" 
href="http://svn.apache.org/repos/asf/commons/proper/commons-sandbox-parent/trunk/pom.xml";>commons-sandbox-parent</a>
-          contains a <tt>trunks-sandbox</tt> profile with the <a 
href="sandbox/index.html">sandbox components</a> set up
-          as <tt>&lt;modules&gt;</tt>. This is a <i>convenience</i> profile so 
that Maven commands can be run
-          for all <a href="sandbox.html">sandbox components</a>.
+        This uses the <tt>src/changes.xml</tt> file to generate the file 
<tt>RELEASE-NOTES.txt</tt>.
+        Requires file <tt>src/changes/release-notes.vm</tt>.
+        A sample template is available from:
+        
https://svn.apache.org/repos/asf/commons/proper/commons-parent/trunk/src/changes/release-notes.vm
        
         </p>
 
         
+<div class="source">
+<pre>mvn changes:announcement-generate -Prelease-notes 
[-Dchanges.version=nnn]</pre></div>
+        
 <p>
-          <b>N.B.</b> This profile works with
-          <a class="externalLink" 
href="http://svn.apache.org/repos/asf/commons/trunks-sandbox/";>http://svn.apache.org/repos/asf/commons/trunks-sandbox/</a>
-          which, you need to check out first (it pulls in the <i>trunks</i> of 
the <a href="sandbox/index.html">sandbox components</a>
-          using an <tt>svn:externals</tt> property - see
-          <a class="externalLink" 
href="http://svnbook.red-bean.com/en/1.1/svn-book.html#svn-ch-7-sect-2.3.6";>here</a>
 for more details).
+          Defining changes.version allows one to create the RN without first 
removing the SNAPSHOT suffix from the POM.
         </p>
+      </div>
 
+      
+<div class="section">
+<h3><a name="javasvn_profile"></a>javasvn profile</h3>
         
 <p>
-          For example, if the template for the 
-          <a class="externalLink" 
href="http://commons.apache.org/commons-build-plugin/sandbox-jira-page.html";>sandbox
 issue tracking page</a>
-          was changed, you could re-generate the issue tracking pages for all 
<a href="sandbox.html">sandbox components</a>
-          using the following command:
+        Optional profile to use javasvn instead of the SVN CLI for the 
buildNumber plugin
         </p>
+      </div>
 
-        
-<div class="source">
-<pre>mvn -Ptrunks-sandbox commons:sandbox-jira-page</pre></div>
-
+      
+<div class="section">
+<h3><a name="Other_profiles_not_intended_for_direct_use"></a>Other profiles, 
not intended for direct use</h3>
         
 <p>
-          ...or to test all sandbox components:
+        The pom also includes some helper profiles that are automatically 
enabled as needed
         </p>
-
         
+<li>
+          
+<ul><tt>jdk7-findbugs</tt> - updates Findbugs version for use under JDK7</ul>
+          
+<ul><tt>svn-buildnumber</tt> - adds the build number to the manifests; 
suppress with 
 <div class="source">
-<pre>mvn -Ptrunks-sandbox clean test</pre></div>
+<pre>-Dbuildnumber.skip</pre></div></ul>
+        </li>
+
       </div>
 
     </div>


Reply via email to