On 13 May 2011 08:47, Torsten Curdt <tcu...@vafer.org> wrote: > Hm ... going through the issues. > > We really need to drop the javac support. It was a hack. But releasing > it as is will be a bit of a pain as it depends on an old jvm to just > pass the tests.
Is it really not possible to implement javac support with a more recent JVM? Doesn't Ant have code to invoke the javac compiler? I've not looked at the code, so I've no idea what it might involve. > Maybe we should shoot for a 2.0 after all and clean things up. *sigh* > > On Fri, May 13, 2011 at 09:06, Torsten Curdt <tcu...@vafer.org> wrote: >> Thanks for checking, Christian. >> >>> I have moved my code base from my old version of jci 1.1 to the trunk and >>> everything looks good. I did have trouble building the trunk, because the >>> fam module is not included in the module list. I have opened JCI-66 to >>> address that. I will take a look at 1.0/1.1 compatibility later this week. >> >> Just wondering - do you require 1.4 compatibility? I would like to >> move to 1.5. Not sure this is the right time for that though. >> >> cheers, >> Torsten >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
