You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@ant.apache.org by bu...@apache.org on 2003/05/13 03:10:06 UTC

DO NOT REPLY [Bug 19875] New: - Undeprecate jvmargs in

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=19875>.
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=19875

Undeprecate jvmargs in <java>

           Summary: Undeprecate jvmargs in <java>
           Product: Ant
           Version: 1.5.2
          Platform: Other
        OS/Version: Other
            Status: NEW
          Severity: Enhancement
          Priority: Other
         Component: Documentation
        AssignedTo: dev@ant.apache.org
        ReportedBy: jefft@apache.org


Hi,

I find it necessary to allow users to specify JVM arguments (-D...=...) outside
the build script, in a properties file. Without @jvmargs, there is no way to
pass a space-separated list of arguments to <java>. Hence I think @jvmargs
should be considered a kosher alternative to multiple <jvmarg> children, and be
un-deprecated.

thanks,

--Jeff