Re: adding to the Java Classpath

Cliff Draper wrote:
> If I change getDesignPath to getBasicPath, it works, but my reading of
> design path sounds more like my jars: jars which are used at compile
> time, but are already deployed in the server.  Should I be using the
> basic path?
> 
Yes.
The "design" path is a convenience abstraction, a merge from various 
sources (IIRC, the source path is there, too), so you can find all 
resources for design-time operations easily.

This behaviour (design path read-only) should be mentioned in the 
javadoc. OR, the behaviour could be refined to forward the add request 
to the basic path -- I don't see a problem with that, but I am off the 
development for some time now, so please check this with Tomas Zezula or 
Honza Pokorsky.

> Also, ClassPath.add says that it will only add the resource if it's
> not there already, but by jars keep getting added anyway.
> 
Bug, please file it.

-Svata