Author: ecki Date: Mon Sep 21 16:00:40 2015 New Revision: 1704337 URL: http://svn.apache.org/viewvc?rev=1704337&view=rev Log: Updated for commons-parent 39 (removed trunks-proper)
Modified: commons/cms-site/trunk/content/xdoc/commons-parent-pom.xml Modified: commons/cms-site/trunk/content/xdoc/commons-parent-pom.xml URL: http://svn.apache.org/viewvc/commons/cms-site/trunk/content/xdoc/commons-parent-pom.xml?rev=1704337&r1=1704336&r2=1704337&view=diff ============================================================================== --- commons/cms-site/trunk/content/xdoc/commons-parent-pom.xml (original) +++ commons/cms-site/trunk/content/xdoc/commons-parent-pom.xml Mon Sep 21 16:00:40 2015 @@ -31,11 +31,11 @@ <a href="http://svn.apache.org/repos/asf/commons/proper/commons-parent/trunk/pom.xml">commons-parent</a> <code>pom.xml</code> <br/> - It has been updated for version 38 of the pom (but some discrepancies may remain). - Please consult <a href="http://svn.apache.org/repos/asf/commons/proper/commons-parent/tags/commons-parent-38/pom.xml">version 38 source</a> + It has been updated for version 39 of the pom (but some discrepancies may remain). + Please consult <a href="http://svn.apache.org/repos/asf/commons/proper/commons-parent/tags/commons-parent-39/">version 39 source</a> in case of doubt. <br/> - Release Notes for <a href="http://svn.apache.org/repos/asf/commons/proper/commons-parent/tags/commons-parent-38/RELEASE-NOTES.txt">version 38</a> + Release Notes for <a href="http://svn.apache.org/repos/asf/commons/proper/commons-parent/tags/commons-parent-39/RELEASE-NOTES.txt">version 39</a> </p> <p> @@ -109,7 +109,8 @@ <strong><a href="#Java_Version">Java Version</a></strong> - <code>source</code> and <code>target</code> options can be configured through <i>properties</i>, and <i>profiles</i> are provided to test on different Java versions. - Where necessary, plugin versions are down-graded to the latest version that runs on earlier JVMs. + Where necessary, plugin versions are down-graded to the latest version that runs on earlier JVMs. If later Java versions + require updated plugins, this is done in a conditional profile (<i>jdk7-plugin-fix-version</i>). </li> <li> <strong><a href="#Testing Coverage">Testing Coverage</a></strong> - both <code>Jacoco</code> and <code>Cobertura</code> @@ -409,6 +410,9 @@ <b><code><Import-Package></code></b> instruction</li> <li>The <b><code><commons.osgi.dynamicImport></code></b> property configures the <b><code><DynamicImport-Package></code></b> instruction</li> + <li>The <b><code><commons.osgi.excludeDependencies></code></b> should be set to + false if the bundle plugin should be able to scan dependency versions and the optional + attribute.</li> </ul> </p> </subsection> @@ -551,38 +555,10 @@ <source>mvn -Prelease package</source> - </subsection> - - <subsection name="trunks-proper profile"> - <p> - <a href="http://svn.apache.org/repos/asf/commons/proper/commons-parent/trunk/pom.xml">commons-parent</a> - contains a <code>trunks-proper</code> profile with the <a href="components.html">components</a> set up - as <code><modules></code>. This is a <i>convenience</i> profile so that Maven commands can be run - for all <a href="components.html">components</a>. - </p> - - <p> - <strong>N.B.</strong> This profile works with - <a href="http://svn.apache.org/repos/asf/commons/trunks-proper/">http://svn.apache.org/repos/asf/commons/trunks-proper/</a> - which, you need to check out first (it pulls in the <i>trunks</i> of the <a href="components.html">components</a> - using an <code>svn:externals</code> property - see - <a href="http://svnbook.red-bean.com/en/1.1/svn-book.html#svn-ch-7-sect-2.3.6">here</a> for more details). - </p> - <p> - For example, if the template for the - <a href="http://commons.apache.org/commons-build-plugin/download-page.html">download page</a> - was changed, you could re-generate the download pages for all <a href="components.html">components</a> - using the following command: - </p> - - <source>mvn -Ptrunks-proper commons:download-page</source> - + You can also combine the <code>-Prelease</code> option with <code>deploy</code> target and the <code>-Ptest-deploy</code> + profile to simulate staging to the repository. <p> - ...or to test all components: - </p> - - <source>mvn -Ptrunks-proper clean test</source> </subsection> <subsection name="release-notes profile">