> > The lib/ directory should contain jars, not classes directly, right? > I agree that lib/*.jar should be added to the classpath, but I was > asking about lib/ itself. Right now if you had > lib/org/apache/axis2/SomeClass.class, that class would be available, > which I do not think is appropriate. Hmm, yes if someone put classes like that it will work . But the whole idea of adding lib directory to classpath is to add resources to lib directory. If you think thats not the right way then I am +1 for your suggestion. > That's what a classes/ directory is for. > >>> 3) Should the classpath actually include the root dir itself? If so, >>> why? >> I think you mean root directory of the archive file , yes we need to do >> so . If someone put some resources under the archive file then he need >> to be able to load them. > > No, I mean the actual modules/ or services/ directory! Unless I'm > reading things incorrectly, Utils.java:209 seems to add the base > directory to the classpath. This gets called 1) once for the repo > base directory itself, 2) once each for services/ and modules/, and > then 3) once for each service. In cases 1 and 2, I believe this > behavior is at least questionable if not incorrect. Oh , same as before lets remove that too.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
