On Fri, Oct 8, 2010 at 9:29 AM, Ed Smiley <[email protected]> wrote:
> Well, it's fine when you understand it, as you can usually get around it. > I do find that allowing Java.classpath to act as if it were writable is > terribly misleading, since any debugging code you add will at as if it had, > indeed been modified. > Fortunately I was skeptical enough to suspect this. Took a while..... > :) Might help to have better documentation of the Java object. > Agreed. I've had this on my documentation TODO list for some time. I've also been meaning to issue a warning when Java.classpath is modified after Java.load has happened. Added an issue to track this: https://issues.apache.org/jira/browse/BUILDR-523 alex
