DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=5307>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=5307

java task: JVM mode cannot be changed while using the jar attribute

[EMAIL PROTECTED] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |FIXED



------- Additional Comments From [EMAIL PROTECTED]  2002-02-02 12:31 -------
Christophe, thanks for reporting. For easier VM debugging in the future you 
might want to set the environment variable _JAVA_LAUNCHER_DEBUG to any value it 
will spit some info to the console which are sometimes useful to identify 
problems, alternatively you can use Ant mode -verbose to look at the invoked 
command line.

For a pertinent answer rather than a gratuitous personal attack toward someone, 
this bug is due to an inconsistency between the JDK documentation, the usage 
command line and what is done in the JDK 1.3.x code when parsing the command 
line (this won't be of any problem in JDK 1.4.x, see below).

Command line says:
Usage: java [-options] class [args...]
           (to execute a class)
   or  java -jar [-options] jarfile [args...]
           (to execute a jar file)
[...]

Documentation says:
   or  java [-options] -jar jarfile [args...]
           (to execute a jar file)

JDK 1.3.x code enforces another order which is none but for the jvmtype that 
must always be the first option. That is:

java [-jvmtype] [-options] [classname|jarfile] args...

This bug has been fixed in JDK 1.4.x, the jvmtype can now be specified anywhere 
as part of the options.

So appending the -jar option rather than prepending as specified in usage 
command line should work since we'll let the burden of specifying correctly the 
jvmtype first to the user for JDK < 1.4.x

I fixed it in CVS now, so you might want to try it.

Alternatively I filled a bug to Sun (139128 and 139129, might take a week to 
appear) since the doc inconsistency still exists in JDK 1.4.rc1 but as any 
order works this is a minor documentation issue. Anyway, we'd better help fix 
things like you do, this is how we make things better. (In a better world..in a 
better place... you know :)

Thanks.

--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to