http://nagoya.apache.org/bugzilla/show_bug.cgi?id=1613
*** shadow/1613 Thu May 3 06:32:54 2001 --- shadow/1613.tmp.18344 Thu May 10 06:43:55 2001 *************** *** 2,8 **** | AntClassLoader doesn't run static initializer blocks | +----------------------------------------------------------------------------+ | Bug #: 1613 Product: Ant | ! | Status: NEW Version: 1.3 | | Resolution: Platform: All | | Severity: Major OS/Version: All | | Priority: Medium Component: Core | --- 2,8 ---- | AntClassLoader doesn't run static initializer blocks | +----------------------------------------------------------------------------+ | Bug #: 1613 Product: Ant | ! | Status: ASSIGNED Version: 1.3 | | Resolution: Platform: All | | Severity: Major OS/Version: All | | Priority: Medium Component: Core | *************** *** 21,24 **** *** Bug 1066 has been marked as a duplicate of this bug. *** ------- Additional Comments From [EMAIL PROTECTED] 2001-05-03 06:32 ------- ! *** Bug 1362 has been marked as a duplicate of this bug. *** --- 21,33 ---- *** Bug 1066 has been marked as a duplicate of this bug. *** ------- Additional Comments From [EMAIL PROTECTED] 2001-05-03 06:32 ------- ! *** Bug 1362 has been marked as a duplicate of this bug. *** ! ! ------- Additional Comments From [EMAIL PROTECTED] 2001-05-10 06:43 ------- ! I've investigated this issue and it is not an Ant specific limitation. Firstly ! it is not the classloader's responsibility to initialize classes (run static ! initializers). It seems that the JDK's Class.forName does initialize the class ! but when a class is loaded through a classloader it is not. Under JDK1.1 there ! is no clean way to force initialization. Attempting to create an instance via ! newInstance does work, even if the instance cannot be created. This will be the ! workaround adopted for Ant 1.x
