Re: Moving to Java 1.5?

[Thilo Goetz <tw...@gmx.de>]

Since there was no disagreement and we have Java 1.5
code in the trunk now, I assume this is official.
Speak now or forever hold your peace.

--Thilo

Michael Baessler wrote:
> Thilo Goetz wrote:
>> Hi all,
>>
>> I'm wondering if it's time to move to Java 1.5 after this
>> release.  While there are still people out there who use
>> Java 1.4, their numbers are shrinking rapidly.  I'm guessing
>> that by the time we do our next release, the need for
>> Java 1.4 compatibility will have gone.
>>
>> I can see three possible courses we could take:
>>
>> 1) Leave things as they are, keep all of the UIMA Java
>> distribution 1.4 compatible.  We should do this if we have
>> reason to believe that demand for 1.4 compatibility will
>> continue for some time to come.
>>
>> 2) Keep the core jars 1.4 compatible, but allow 1.5 constructs
>> in our tools.  I'm saying this because I was thinking of
>> doing some improvements to CVD where I might want to use 1.5.
>> However, I don't like this approach myself as it complicates
>> our build process.
>>
>> 3) Allow Java 1.5 constructs everywhere (and change our build
>> accordingly).  If the developers are all agreed to do this,
>> we should also check what the folks on uima-user think.
>>
>> Let me know what you think.
> I'm also fine with moving to Java 1.5. But I don't like the idea 2). I
> think mixed Java versions in one distribution
> might confuse the users. In this case, I think we can use the Sandbox
> for components that have to use Java 1.5.
> 
> --Michael