ant-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Phillip.We...@dresdnerkb.com
Subject RE: JUnitReport classpath problem (again!)
Date Mon, 05 Mar 2001 10:55:43 GMT
Aha! Found the problem. Seems that in 1.3b3 you could just rename jaxp.jar
and parser.jar to stop Ant picking them up. In 1.3, however, they actually
need to be deleted from the /lib directory for the task to work.

-----Original Message-----
From: Stephane Bailliez [mailto:sbailliez@imediation.com]
Sent: 05 March 2001 10:52
To: ant-user@jakarta.apache.org
Subject: RE: JUnitReport classpath problem (again!)




Check your classpath again please. 

This looks like jaxp.jar/parser.jar are still on the classpath. 
use -verbose or ultimately -debug 

All I can recommend is to have a - unique parser - in your classpath,
otherwise whatever you do, you put yourself in a dangerous situation.

Even doing this is not a guarantee since most parser packages give you the
sax and dom interfaces and implementation, so you will have it several times
in your classpath and you will likely end up with a classloader violation
constraint or a package sealing violation. And I'm not counting other app
that also stuff sax/dom classes into their jar...

This is only the beginning... 

Hope it helps. 

-- 
 St├ęphane Bailliez 
 Software Engineer, Paris - France 
 iMediation - http://www.imediation.com <http://www.imediation.com>  
 Disclaimer: All the opinions expressed above are mine and not those from my
company. 



> -----Original Message----- 
> From: Phillip.Wells@dresdnerkb.com 
> [ mailto:Phillip.Wells@dresdnerkb.com
<mailto:Phillip.Wells@dresdnerkb.com> ] 
> Sent: Monday, March 05, 2001 11:22 AM 
> To: ant-user@jakarta.apache.org 
> Subject: JUnitReport classpath problem (again!) 
> 
> 
> I had JUnitReport working in 1.3b3 by removing parser.jar and 
> jaxp.jar and 
> making sure xalan.jar (1.2.2) and xerces.jar were on my 
> classpath instead. 
> Since installing 1.3 this morning however, this no longer 
> works and I'm 
> getting errors like 
> 
> XSL Error: Cannot use a DTMLiaison for a input DOM node... pass a 
> org.apache.xal 
> an.xpath.xdom.XercesLiaison instead! 
> XSL Error: SAX Exception 
> org.apache.xalan.xslt.XSLProcessorException: 
>         at 
> org.apache.xalan.xslt.XSLTEngineImpl.error(XSLTEngineImpl.java:1799) 
>         at 
> org.apache.xalan.xslt.XSLTEngineImpl.error(XSLTEngineImpl.java:1691) 
>         at 
> org.apache.xalan.xslt.XSLTEngineImpl.getSourceTreeFromInput(XSLTEngin 
> eImpl.java:919) 
>         at 
> org.apache.xalan.xslt.XSLTEngineImpl.process(XSLTEngineImpl.java, 
> Com 
> piled Code) 
>         at 
> org.apache.tools.ant.taskdefs.optional.junit.AggregateTransformer.tra 
> nsform(AggregateTransformer.java:460) 
>         at 
> org.apache.tools.ant.taskdefs.optional.junit.AggregateTransformer.cre 
> atePackageList(AggregateTransformer.java:310) 
>         at 
> org.apache.tools.ant.taskdefs.optional.junit.AggregateTransformer.tra 
> nsform(AggregateTransformer.java:233) 
>         at 
> org.apache.tools.ant.taskdefs.optional.junit.XMLResultAggregator.exec 
> ute(XMLResultAggregator.java, Compiled Code) 
>         at org.apache.tools.ant.Target.execute(Target.java, 
> Compiled Code) 
>         at org.apache.tools.ant.Project.runTarget(Project.java:898) 
>         at 
> org.apache.tools.ant.Project.executeTarget(Project.java, Compiled 
> Cod 
> e) 
>         at org.apache.tools.ant.Project.executeTargets(Project.java, 
> Compiled Co 
> de) 
>         at org.apache.tools.ant.Main.runBuild(Main.java, 
> Compiled Code) 
>         at org.apache.tools.ant.Main.main(Main.java:149) 
> 
> BUILD FAILED 
> 
> What should be on the classpath, what shouldn't and in what order? 
> 
> Phil. 
> 
> 
> ---------------------------------------------------------------------- 
> If you have received this e-mail in error or wish to read our e-mail 
> disclaimer statement and monitoring policy, please refer to 
> http://www.drkw.com/disc/email/ <http://www.drkw.com/disc/email/>  or
contact the sender. 
> ---------------------------------------------------------------------- 
> 



----------------------------------------------------------------------
If you have received this e-mail in error or wish to read our e-mail 
disclaimer statement and monitoring policy, please refer to 
http://www.drkw.com/disc/email/ or contact the sender.
----------------------------------------------------------------------

Mime
View raw message