On Thu, 2004-04-29 at 11:21, [EMAIL PROTECTED] wrote: > Thanks, that solved the problem. > > Why on earth does it make a difference where a jar is located? :-(
Because class loaders are arranged in a hierarchy, a class can only see classes from his loader or his parent loaders. I don't know what's the problem in the below scenario though. > > Bye, Helma > > > -----Original Message----- > > From: Juan Jose Pablos [mailto:[EMAIL PROTECTED] > > Sent: Thursday, 29 April 2004 11:15 > > To: [EMAIL PROTECTED] > > Subject: Re: build failed on JavaFlow in current CVS HEAD > > > > > > Hi, > > [EMAIL PROTECTED] escribi�: > > > > > D:\cvs\cocoon-2.1\src\blocks\javaflow\java\org\apache\cocoon\component > > > s\flow > > > \java\ContinuationClassLoader.java:100: cann > > > ot resolve symbol > > > symbol : method setRepository > > (org.apache.bcel.util.ClassLoaderRepository) > > > location: class org.apache.bcel.Repository > > > Repository.setRepository(new ClassLoaderRepository(parent)); > > > ^ > > > > > > Try to move jakarta-bcel-20040329.jar from lib/core to > > lib/endorsed and > > try to compile again. > > > > Cheers, > > Cheche > > -- Bruno Dumon http://outerthought.org/ Outerthought - Open Source, Java & XML Competence Support Center [EMAIL PROTECTED] [EMAIL PROTECTED]
