This is the mail archive of the
mailing list for the Mauve project.
Re: Java 5 features
- From: Tom Tromey <tromey at redhat dot com>
- To: Michael Koch <konqueror at gmx dot de>
- Cc: classpath at gnu dot org, mauve-discuss at sources dot redhat dot com
- Date: 08 Mar 2006 10:30:24 -0700
- Subject: Re: Java 5 features
- References: <20060307193846.GL18158@asterix.konqueror.de>
- Reply-to: tromey at redhat dot com
>>>>> "Michael" == Michael Koch <firstname.lastname@example.org> writes:
Michael> What is the state of support for the Java 5 language features
Michael> in Mauve? Is it okay to use Generics and Enums and such
Michael> stuff in testcases that are tagged "1.5"? I would like to
Michael> commit some testcases that use Generics and Enums to test
Michael> some stuff in GNU classpath generics branch.
Michael> What's your opinion?
The problem with doing this is that it means that parts of Mauve
won't compile against classpath head. This in turn means that an
eclipse checkout will always show errors.
I suppose if we put these tests into a segregated part of the
directory tree we could easily turn them off in the eclipse build.
Perhaps we could just disable eclipse compilation of individual
files, I haven't looked...
Another idea would be to make a generics branch for mauve and then
merge it when we do the merge for classpath.