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 wrote:
> I'm curious to see the spec; Java::Commands.java always forks a new java
> process so it shouldn't chan
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 wrote:
> I am writing specs for the javac command and I am finding out t
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 discov
