I think that using Sun's javac and Eclipse with their undocumented and unsupported options during the "transition period" seems the cleanest strategy for both class library and VM maintenance. I see no trouble having such a dependency for a limited period of time (a few months).
Etienne Geir Magnusson Jr wrote: > Tim Ellison wrote: >> Using the Eclipse compiler: >> >> In the Eclipse JDT UI you *can* specify source=5.0 target=1.4 and I >> successfully ran code written using generics on a 1.4 VM. However, the >> Eclipse batch compiler does not allow this source=5.0 target=1.4 >> combination; and when I asked why the answer was that the UI usage is >> wrong and will be fixed to prevent that combination. > > LOL! How about suggesting that users find it useful right now? >... > It seems like we have two options - Sun and Eclipse, and because the > eclipse compiler is CDDL, and can be integrated into our build system, > we seem to be safe. -- Etienne M. Gagnon, Ph.D. http://www.info2.uqam.ca/~egagnon/ SableVM: http://www.sablevm.org/ SableCC: http://www.sablecc.org/
signature.asc
Description: OpenPGP digital signature
