commons-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From s...@apache.org
Subject svn commit: r1653294 - /commons/cms-site/trunk/content/xdoc/commons-parent-pom.xml
Date Tue, 20 Jan 2015 16:50:08 GMT
Author: sebb
Date: Tue Jan 20 16:50:08 2015
New Revision: 1653294

URL: http://svn.apache.org/r1653294
Log:
Tweaks

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=1653294&r1=1653293&r2=1653294&view=diff
==============================================================================
--- commons/cms-site/trunk/content/xdoc/commons-parent-pom.xml (original)
+++ commons/cms-site/trunk/content/xdoc/commons-parent-pom.xml Tue Jan 20 16:50:08 2015
@@ -60,9 +60,9 @@
             specifies the Plugin versions to be used in the <code>&lt;pluginManagement&gt;</code>
section.
             <ul>
               <li>
-                (<b>N.B.</b> the <code>&lt;reporting&gt;</code>
section ignores whats specified in the
+                (<b>N.B.</b> the <code>&lt;reporting&gt;</code>
section ignores anything specified in the
                 <code>&lt;pluginManagement&gt;</code> section and component
pom.xml's should specify the version of
-                additional reports they specify).
+                any additional report plugins they specify).
               </li>
             </ul>
           </li>
@@ -71,7 +71,7 @@
             produced by the build to conform with the <a href="http://www.apache.org/dev/release.html#license">ASF
License Policy</a>.
           </li>
           <li>
-            <strong><code>MANIFEST.MF</code> files</strong> - The
information is automatically included in the componentjar's manifest file:
+            <strong><code>MANIFEST.MF</code> files</strong> - The
following information is automatically included in the componentjar's manifest file:
             <ul>
               <li><code>Implementation-Title</code> - set to the component's
name</li>
               <li><code>Implementation-Vendor</code> - set to <i>The
Apache Software Foundation</i></li>
@@ -104,9 +104,9 @@
           </li>
           <li>
             <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
+            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.
+            Where necessary, plugin versions are down-graded to the latest version that runs
on earlier JVMs.
           </li>
           <li>
             <strong><a href="#Testing Coverage">Testing Coverage</a></strong>
- both <code>Jacoco</code> and <code>Cobertura</code>
@@ -236,7 +236,7 @@
               <maven.compiler.target>1.4</maven.compiler.target>
           </properties> 
         ]]></source>
-          <b>NOTE:</b> the Maven compiler plugin defaults to 
+          <b>NOTE:</b> the Maven compiler plugin defaults to using the properties
           <code>${maven.compiler.source}</code> and <code>${maven.compiler.target}</code>;
however the
           Commons Parent POM originally incorrectly used ".compile." rather than ".compiler."
           This was fixed in version 31 of the Commons Parent pom.
@@ -249,11 +249,11 @@
           configure the <i>source/target</i> options in the 
           <a href="http://maven.apache.org/plugins/maven-compiler-plugin/">maven-compiler-plugin</a>
           (i.e. <code>${maven.compiler.source}</code> and <code>${maven.compiler.target}</code>)
are also written
-          out to the component jar's <code>MANIFEST.MF</code> file with the following
values:
+          out to the component jar's <code>MANIFEST.MF</code> file with the following
header names:
         </p>
         <source>
-            X-Compile-Source-JDK: 1.4
-            X-Compile-Target-JDK: 1.4
+            X-Compile-Source-JDK:
+            X-Compile-Target-JDK:
         </source>
       </subsection>
 
@@ -261,11 +261,12 @@
         <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
-          introduced in later Java versions (because the build will use the current Java
libraries by default).
+          introduced in later Java versions (this is because the build will use the current
Java libraries by default).
           One way to ensure that components don't accidentally use classes/methods from a
later
-          version of Java is to compile and test using actual Java versions.
+          version of Java is to compile and test using the actual target Java version.
         </p>
         <p>
+          However, it may be that one or more Maven  plugins require a later version of Java
than the component.
           For this reason
           <a href="http://svn.apache.org/repos/asf/commons/proper/commons-parent/trunk/pom.xml">commons-parent</a>
           provides <i>profiles</i> for compiling/testing under different Java
versions (correct as of version 36):



Mime
View raw message