commons-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From nia...@apache.org
Subject svn commit: r922630 - /commons/proper/commons-site/src/site/xdoc/commons-parent-pom.xml
Date Sat, 13 Mar 2010 17:58:33 GMT
Author: niallp
Date: Sat Mar 13 17:58:33 2010
New Revision: 922630

URL: http://svn.apache.org/viewvc?rev=922630&view=rev
Log:
Revert the subsection title. minor corrections and remove the <_removeheaders> comment
from the Custom OSGi configuration section (its inappropriate since this is dealing with Compoinent's
custom config - as oppose to using the default defined in the commons-parent pom)

Modified:
    commons/proper/commons-site/src/site/xdoc/commons-parent-pom.xml

Modified: commons/proper/commons-site/src/site/xdoc/commons-parent-pom.xml
URL: http://svn.apache.org/viewvc/commons/proper/commons-site/src/site/xdoc/commons-parent-pom.xml?rev=922630&r1=922629&r2=922630&view=diff
==============================================================================
--- commons/proper/commons-site/src/site/xdoc/commons-parent-pom.xml (original)
+++ commons/proper/commons-site/src/site/xdoc/commons-parent-pom.xml Sat Mar 13 17:58:33 2010
@@ -227,7 +227,7 @@
         </source>
       </subsection>
 
-      <subsection name="Compiling / Testing with different Java versions">
+      <subsection name="Testing with different Java versions">
         <p>
           Using the <i>target</i> option ensures that the <code>.class</code>
file format is compatible with
           the required Java version - but it does not prevent/catch the use of methods/classes
which were
@@ -254,12 +254,12 @@
           for details. Each property should be set to the <code>directory</code>
where the relevant version of the JDK is installed.
         </p>
         <p>
-          Note that the <a href="http://felix.apache.org/site/apache-felix-maven-bundle-plugin-bnd.html">maven-bundle-plugin</a>
-          copies will output all property values which start with a capital letter as headers
in jar's <code>MANIFEST.MF</code> file.
+          <b>Note:</b> the <a href="http://felix.apache.org/site/apache-felix-maven-bundle-plugin-bnd.html">maven-bundle-plugin</a>
+          outputs all property values which start with a capital letter as headers to the
jar's <code>MANIFEST.MF</code> file.
           The commons-parent pom uses the &lt;_removeheaders&gt; instruction to suppress
the specific JAVA_* properties used by the pom.
         </p>
         <p>
-          To ensure that the properties are only defined if they are actually needed, you
can
+          To ensure that the properties are only present if they are actually needed, you
can
           define the property in the relevant profile in your <code>settings.xml</code>,
for example:
         </p>
         <source><![CDATA[
@@ -359,8 +359,6 @@
                 <b><code>&lt;Import-Package&gt;</code></b>
instruction</li>
              <li>The <b><code>&lt;commons.osgi.dynamicImport&gt;</code></b>
property configures the
                 <b><code>&lt;DynamicImport-Package&gt;</code></b>
instruction</li>
-             <li>As mentioned above, the <b><code>&lt;_removeheaders&gt;</code></b>
instruction is used 
-                 to prevent the known JAVA_1_*_HOME properties from appearing as headers
in the manifest.</li>
           </ul>
         </p>
       </subsection>



Mime
View raw message