harmony-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From George Harley <george.c.har...@googlemail.com>
Subject Re: [classlib] Switching to a 5.0 compiler
Date Wed, 05 Apr 2006 12:28:49 GMT

Using the Sun 5.0 javac with the "jsr14" target it is possible to do a 
complete compile of the Harmony Java source and successfully run the 
tests on the existing VME. That means we could add in more contributions 
that depended on 5.0 language features being understood instead of 
letting them queue up.

So +1 from me for using the straightforward but undocumented "jsr14" 
target as a purely temporary measure to keep things moving onwards.

Best regards,

Etienne Gagnon wrote:
> 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.

Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: harmony-dev-unsubscribe@incubator.apache.org
For additional commands, e-mail: harmony-dev-help@incubator.apache.org

View raw message