Wouldn't it bee sufficient to add support for the -bootclasspath and -extdirs options? That might not be as convenient as simply calling javac of another installed jdk of course since you would have to puzzle together those two parameters yourself rather than getting the defaults.
Pepijn On 22 Mar 2010, at 20:25, Antoine Toulme wrote: > They do - but javax.sql did change in jdk6. Hibernate doesn't implement all > the right methods with it then. > > That's just one example. > > I understand that there is no interest in pushing for that effort. I'll make > a contribution of the external javac compiler, will ask for code review. > > Thanks, > > Antoine > > On Mon, Mar 22, 2010 at 12:19, Charles Oliver Nutter > <[email protected]>wrote: > >> On Sun, Mar 21, 2010 at 2:24 PM, Antoine Toulme <[email protected]> >> wrote: >>> This compiler helps me as I need to use a different JDK for part of the >>> projects I have to compile. >> >> Why do you need to do that? All current Java releases support >> compiling code for older JVMs... >> >> ~/projects/jruby ➔ javac 2>&1 | grep release >> -source <release> Provide source compatibility with specified >> release >> -target <release> Generate class files for specific VM version >> >> ~/projects/jruby ➔ javac -version >> javac 1.6.0_17 >> >> - Charlie >>
