ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject [Bug 1556] Changed - ClassLinkageError while testing classes which use JAXP classes
Date Thu, 10 May 2001 14:34:37 GMT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=1556

*** shadow/1556	Fri Apr 27 09:14:52 2001
--- shadow/1556.tmp.18485	Thu May 10 07:34:37 2001
***************
*** 2,8 ****
  | ClassLinkageError while testing classes which use JAXP classes             |
  +----------------------------------------------------------------------------+
  |        Bug #: 1556                        Product: Ant                     |
! |       Status: NEW                         Version: 1.3                     |
  |   Resolution:                            Platform: PC                      |
  |     Severity: Normal                   OS/Version: Linux                   |
  |     Priority: Low                       Component: Optional Tasks          |
--- 2,8 ----
  | ClassLinkageError while testing classes which use JAXP classes             |
  +----------------------------------------------------------------------------+
  |        Bug #: 1556                        Product: Ant                     |
! |       Status: ASSIGNED                    Version: 1.3                     |
  |   Resolution:                            Platform: PC                      |
  |     Severity: Normal                   OS/Version: Linux                   |
  |     Priority: Low                       Component: Optional Tasks          |
***************
*** 81,84 ****
  Happy bughunting...
  
  Janne Kario
! <kario@mermit.fi>
--- 81,97 ----
  Happy bughunting...
  
  Janne Kario
! <kario@mermit.fi>
! 
! ------- Additional Comments From conor@cortexebusiness.com.au  2001-05-10 07:34 -------
! Can you try forking the junit task (running junit with fork="yes"). You'll need 
! to add the ant junit classes into the classpath when you do. 
! 
! Your analysis is close to the mark. The classes when they are loaded are 
! violating loader constraints. These come about when a class in one loader 
! refers to methods or fields in a class loaded by another loader. It is 
! difficult to avoid when the package namespaces of the classloaders (system and 
! junit task) overlap.
! 
! Forking is usually effective. If so, please let me know and I will close this 
! bug.

Mime
View raw message