svn commit: r171039 - /jakarta/commons/proper/commons-build/trunk/xdocs/releases/prepare.xml

[sk...@apache.org]

Author: skitching
Date: Thu May 19 20:10:29 2005
New Revision: 171039

URL: http://svn.apache.org/viewcvs?rev=171039&view=rev
Log:
Added info re setting compile options to support old JVM versions

Modified:
    jakarta/commons/proper/commons-build/trunk/xdocs/releases/prepare.xml

Modified: jakarta/commons/proper/commons-build/trunk/xdocs/releases/prepare.xml
URL: http://svn.apache.org/viewcvs/jakarta/commons/proper/commons-build/trunk/xdocs/releases/prepare.xml?rev=171039&r1=171038&r2=171039&view=diff
==============================================================================
--- jakarta/commons/proper/commons-build/trunk/xdocs/releases/prepare.xml (original)
+++ jakarta/commons/proper/commons-build/trunk/xdocs/releases/prepare.xml Thu May 19 20:10:29 2005
@@ -345,6 +345,16 @@
     <li>Javadoc errors</li>
     <li>Missing LICENSE.txt or NOTICE.txt files</li>
     <li>Failing to run the checkstyle report for projects that use checkstyle</li>
+    <li>
+      Building on a more recent JVM than the code will run on. Java class file
+      format has changed a number of times over the years, and code compiled with
+      a modern JVM may fail to load in an older JVM with the error message
+      "invalid class file format" unless the code is compiled with appropriate
+      options set. If you are using Maven, then ensure that project.properties
+      has maven.compile.target set to the minimum JVM version your binary is
+      intented to support. If you are using Ant, then ensure that the javac task
+      has xml attribute "target" is set to the appropriate JVM version.
+    </li>
     </ul>
   </section>
 



---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org