You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by bu...@apache.org on 2001/02/01 10:42:21 UTC

[Bug 222] New - Ant fails to verify class with static initializer code during rmic task BugRat Report#343

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=222

*** shadow/222	Thu Feb  1 01:42:21 2001
--- shadow/222.tmp.8555	Thu Feb  1 01:42:21 2001
***************
*** 0 ****
--- 1,18 ----
+ +============================================================================+
+ | Ant fails to verify class with static initializer code during rmic task Bu |
+ +----------------------------------------------------------------------------+
+ |        Bug #: 222                         Product: Ant                     |
+ |       Status: UNCONFIRMED                 Version: 1.2                     |
+ |   Resolution:                            Platform: All                     |
+ |     Severity: Normal                   OS/Version: All                     |
+ |     Priority: High                      Component: Main                    |
+ +----------------------------------------------------------------------------+
+ |  Assigned To: ant-dev@jakarta.apache.org                                   |
+ |  Reported By: anonymous-bug@cortexity.com                                  |
+ |      CC list: Cc:                                                          |
+ +----------------------------------------------------------------------------+
+ |          URL:                                                              |
+ +============================================================================+
+ |                              DESCRIPTION                                   |
+ Don't know exactly if this is considerable as a bug:
+ I have a class with static initializer code that depends on previous assignment of a system property: so, when the "verify" part of the rmic task loads the class in order to decide whether it should be rmi-compiled, the initializer is executed, and a ExceptionInInitializerError is thrown, thus stopping the build (build failed). I think this exception should be silently catched (or at least signaled without stopping the build).