commons-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From s...@apache.org
Subject svn commit: r947619 - /commons/proper/commons-site/trunk/src/site/xdoc/releases/prepare.xml
Date Mon, 24 May 2010 12:25:57 GMT
Author: sebb
Date: Mon May 24 12:25:57 2010
New Revision: 947619

URL: http://svn.apache.org/viewvc?rev=947619&view=rev
Log:
Add references to the java-1.x profiles
No longer using Maven-1 so Ant props need to agree with pom.xml

Modified:
    commons/proper/commons-site/trunk/src/site/xdoc/releases/prepare.xml

Modified: commons/proper/commons-site/trunk/src/site/xdoc/releases/prepare.xml
URL: http://svn.apache.org/viewvc/commons/proper/commons-site/trunk/src/site/xdoc/releases/prepare.xml?rev=947619&r1=947618&r2=947619&view=diff
==============================================================================
--- commons/proper/commons-site/trunk/src/site/xdoc/releases/prepare.xml (original)
+++ commons/proper/commons-site/trunk/src/site/xdoc/releases/prepare.xml Mon May 24 12:25:57
2010
@@ -334,10 +334,16 @@
 	If you are using Maven to execute the unit tests associated with the component then
 	there is nothing to do here; Maven will automatically perform the tests using the
 	library versions specified in the project.xml file.
+    </p>
+    <p>
+    It's also vital to ensure that you test against the correct version of the Java libraries.
+    If Maven requires a later version of Java, then use the appropriate <code>java-1.x</code>
profile.
+    See <a href="../commons-parent-pom.html#Testing_with_different_Java_versions">Testing
with different Java versions</a>
+    for further details.
 	</p>
     <p>
-    If you are using Ant to execute unit tests, then ensure the Ant build.xml file
-	references the same library versions as are listed as dependencies in the project.xml
+    If you are using Ant to execute unit tests, then ensure the Ant <code>build.xml</code>
file
+	references the same library versions as are listed as dependencies in the <code>pom.xml</code>
 	file then execute the unit tests.
 	</p>
     </subsection>
@@ -441,7 +447,17 @@
       this always ensures a clean copy is made.
     </p>
 	<p>
-	Build distributions from a fresh checkout of the RC tag. 
+	Build distributions from a fresh checkout of the RC tag.
+    Build the code with the target version of Java if possible.<br />
+    If the version of Maven you are using requires a more recent version of Java than the
code you are
+    building, then use the appropriate <code>java-1.x</code> profile to ensure
that compilation and testing is done
+    with the correct Java version. This will catch any accidental use of methods etc. that
are not in
+    the target Java version libraries. 
+    See <a href="../commons-parent-pom.html#Testing_with_different_Java_versions">Testing
with different Java versions</a>
+    for further details.
+    (the compiler.source and compiler.target versions only affect source syntax and class
file format)
+    </p>
+    <p>
 	Post the release candidate into the public folder <em>~/public_html</em> in
your home directory 
     on <code>people.apache.org</code>.
     </p>



Mime
View raw message