ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 19150] - Command-line argument "jvmarg" attribute "file" not working.
Date Thu, 24 Apr 2003 11:56:04 GMT
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=19150>.
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=19150

Command-line argument "jvmarg" attribute "file" not working.





------- Additional Comments From bodewig@apache.org  2003-04-24 11:56 -------
It may depend on the Java VM.  It could be that java in some future version
will have a command line option that takes an additional file argument.

OK, this has lead me to construct an esoteric use-case:

<java classname="...">
  <jvmarg value="-classpath"/>
  <jvmarg file="build/my.jar"/>
</java>

will invoke java with the arguments -classpath FULL-PATH-TO/build/my.jar.

In this case, it will not lead to the error message you've seen.  It is not
a good use-case (and I don't know of any good one, I already said so), but it
is an expamle where the outcome is not the NoClassDefFoundError.

If Java 47.11 is going to have an option -paramfile that expects a filename
as additional parameter, the file attribute of jvmarg has suddenly become
useful.

Mime
View raw message