http://nagoya.apache.org/bugzilla/show_bug.cgi?id=1035
*** shadow/1035 Mon Mar 19 17:19:00 2001 --- shadow/1035.tmp.9124 Mon Mar 19 23:55:12 2001 *************** *** 2,11 **** | javac throws exception when using JDK1.3 | +----------------------------------------------------------------------------+ | Bug #: 1035 Product: Ant | ! | Status: NEW Version: 1.1 | ! | Resolution: Platform: PC | ! | Severity: Normal OS/Version: | ! | Priority: Component: Core tasks | +----------------------------------------------------------------------------+ | Assigned To: [EMAIL PROTECTED] | | Reported By: [EMAIL PROTECTED] | --- 2,11 ---- | javac throws exception when using JDK1.3 | +----------------------------------------------------------------------------+ | Bug #: 1035 Product: Ant | ! | Status: RESOLVED Version: 1.1 | ! | Resolution: LATER Platform: PC | ! | Severity: Normal OS/Version: All | ! | Priority: High Component: Core tasks | +----------------------------------------------------------------------------+ | Assigned To: [EMAIL PROTECTED] | | Reported By: [EMAIL PROTECTED] | *************** *** 12,17 **** --- 12,18 ---- | CC list: Cc: | +----------------------------------------------------------------------------+ | URL: | + | Dependencies: BugsThisDependsOn: 383[] | +============================================================================+ | DESCRIPTION | While building a project using ANT 1.3 the build process failed on [javac] with *************** *** 63,66 **** file before the exception was thrown. I can successfully compile this source code by running javac directly from the ! command line but not via ANT. --- 64,77 ---- file before the exception was thrown. I can successfully compile this source code by running javac directly from the ! command line but not via ANT. ! ! ------- Additional Comments From [EMAIL PROTECTED] 2001-03-19 23:55 ------- ! Duplicate of 383. ! ! The problem is, that you modify a JAR file and try to use this modified version ! later. ! ! Until <javac> can be forked into a separate VM or uses a classloader of its own, ! you cannot avoid this problem. I think, apart from using <exec> to invoke javac, ! you've pretty much covered all workarounds.
