Oh, sorry, you're talking about javac... but same thing, I'm not seeing it. Maybe you can open an issue and attach your spec?
alex On Sat, Aug 28, 2010 at 5:29 PM, Alex Boisvert <[email protected]>wrote: > I'm curious to see the spec; Java::Commands.java always forks a new java > process so it shouldn't change the current application classpath. > > Maybe I'm missing something? > > alex > > > > On Sat, Aug 28, 2010 at 5:11 PM, Antoine Toulme > <[email protected]>wrote: > >> I am writing specs for the javac command and I am finding out that it >> resets >> the classpath of the application, since you pass a classpath to it. >> >> At this point, it sounds like the safest option is to shell out instead of >> running javac in the current JVM, as it has some nasty side effects. >> >> I discovered the problem when I tried to run several specs that were >> calling >> javac in the same file. >> >> This might not happen with JRuby but I wouldn't take chances on it. >> >> Let me know if you have strong objections ; I'll commit soon but it can be >> reverted. >> >> Antoine >> > >
