ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject [Bug 222] Changed - Ant fails to verify class with static initializer code during rmic task BugRat Report#343
Date Sun, 04 Feb 2001 14:47:44 GMT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=222

*** shadow/222	Thu Feb  1 03:54:32 2001
--- shadow/222.tmp.1403	Sun Feb  4 06:47:44 2001
***************
*** 2,8 ****
  | 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: Core tasks              |
--- 2,8 ----
  | Ant fails to verify class with static initializer code during rmic task Bu |
  +----------------------------------------------------------------------------+
  |        Bug #: 222                         Product: Ant                     |
! |       Status: NEW                         Version: 1.2                     |
  |   Resolution:                            Platform: All                     |
  |     Severity: Normal                   OS/Version: All                     |
  |     Priority: High                      Component: Core tasks              |
***************
*** 15,18 ****
  +============================================================================+
  |                              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).
--- 15,30 ----
  +============================================================================+
  |                              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).
! 
! ------- Additional Comments From nico@apache.org  2001-02-04 06:47 -------
! Only happens when using JDK < 1.2. (Tested with JDK 1.1.7, JDK 1.1.8 (IBM), JDK 
! 1.2, JDK 1.2.2, JDK 1.3 all on W2K+SP1).
! 
! Just rmic'd a class which contained a static initializer which looks like this:
! 
! static {
!     if (true){
!          throw new NullPointerException();
!     }
! }

Mime
View raw message