http://nagoya.apache.org/bugzilla/show_bug.cgi?id=1113
*** shadow/1113 Tue Mar 27 01:01:37 2001 --- shadow/1113.tmp.17497 Tue Mar 27 02:13:01 2001 *************** *** 2,9 **** | Using the args attribute in the wlrun task | +----------------------------------------------------------------------------+ | Bug #: 1113 Product: Ant | ! | Status: NEW Version: 1.3 | ! | Resolution: Platform: PC | | Severity: Minor OS/Version: All | | Priority: High Component: Optional Tasks | +----------------------------------------------------------------------------+ --- 2,9 ---- | Using the args attribute in the wlrun task | +----------------------------------------------------------------------------+ | Bug #: 1113 Product: Ant | ! | Status: RESOLVED Version: 1.3 | ! | Resolution: INVALID Platform: PC | | Severity: Minor OS/Version: All | | Priority: High Component: Optional Tasks | +----------------------------------------------------------------------------+ *************** *** 52,55 **** This problem can be overcome by putting all arguments into the wlrun attribute jvmargs. Note that this is also a problem in release 1.3 ! Mick --- 52,63 ---- This problem can be overcome by putting all arguments into the wlrun attribute jvmargs. Note that this is also a problem in release 1.3 ! Mick ! ! ------- Additional Comments From [EMAIL PROTECTED] 2001-03-27 02:13 ------- ! Mick, if the arguments are for the JVM, then jvmargs is where they should go. ! If the arguments are for the server itself, then args is appropriate. I ! actually don't know if the server itself takes any args, but the capability is ! there. So, I don't think this is a problem. I'm going to mark as invalid. If I ! have completely misunderstood the issue, please reopen. Maybe the documentation ! needs to be clearer - let me know.
