kaz 02/05/06 08:22:34
Modified: xdocs/ref faq.xml
Log:
Added an FAQ entry about Checkstyle crapping out on IBM's 1.3.0 JVM,
thanks to leandro for isolating this.
Revision Changes Path
1.4 +22 -0 jakarta-turbine-maven/xdocs/ref/faq.xml
Index: faq.xml
===================================================================
RCS file: /home/cvs/jakarta-turbine-maven/xdocs/ref/faq.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- faq.xml 6 May 2002 02:03:31 -0000 1.3
+++ faq.xml 6 May 2002 15:22:34 -0000 1.4
@@ -50,6 +50,12 @@
</a>
</li>
<li>
+ <a href="#check-source-ibm-130">
+ Why does <code>maven:check-source</code> fail for no apparent
+ reason when using IBM's 1.3.0 JVM?
+ </a>
+ </li>
+ <li>
<a href="#check-source-no-memory">
Why does <code>maven:check-source</code> fail with the
following exception: Out of Memory?
@@ -186,6 +192,22 @@
<code>checkstyle.rcurly</code> to <code>same</code>.
Please refer to the <a href="properties.html#Checkstyle Settings">
Properties</a> document for more information on these settings.
+ </dd>
+ <dt>
+ <a name="check-source-ibm-130"> Why does
+ <code>maven:check-source</code> fail for no apparent
+ reason when using IBM's 1.3.0 JVM?
+ </a>
+ </dt>
+ <dd>
+ There is a known problem where IBM's 1.3.0 JVM fails during
+ the <code>maven:check-source</code> target. Unfortunately, we
+ do not have a workaround at this moment other than updating
+ your JVM. This is the output of <code>java -version</code>
+ from IBM JVM:
+ <pre>
+ Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.0)
+ Classic VM (build 1.3.0, J2RE 1.3.0 IBM build cx130-20010626 (JIT enabled:
jitc))</pre>
</dd>
<dt>
<a name="dvsl-resource-not-an-error">
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
