I agree with the approach. Namely - officially schedule Java 5 switch
to happen after 3.0M2 release. I wouldn't mind doing the actual merge
of the modules myself.
On the user end, we only had one user who needed JDK 1.4
compatibility. What I realized now is that he was eyeing 3.0 (vs.
2.0) is because their organization wanted to use annotations/POJO's
down the road. Which implies Java 5. (Ok, I guess theoretically we
can do pre-enhancement of POJO's via Ant and do not rely on
instrumentation API - I guess I'll follow up on the user list).
Also I don't think we need to re-vote. There is an official vote
confirming the consensus that 3.0 final should be Java 5 only. I
think we can iron out the details on the list without voting.
Andrus
On Sep 14, 2007, at 5:57 AM, Kevin Menard wrote:
> On 9/13/07 6:45 PM, "Aristedes Maniatis" <ar..aniatis.org> wrote:
>
>
>> Since I was the only slightly negative voice in this thread, I'd like
>> to say that I'm mostly convinced by the arguments, so I'll vote +0.
>> That is, I don't think it is important to do it now, but if it will
>> help others, let's go for it.
>>
>> As for timeframe, perhaps that happens whenever someone puts in the
>> effort to merge the 1.4 and 1.5 frameworks into one.
>
> Great. I think your suggestion makes sense, too. At the very
> least, I'd
> expect we put out a 1.4-compatible 3.0M2 to help those that need to,
> transition.
>
> --
> Kevin
>
>
>
This archive was generated by hypermail 2.0.0 : Fri Sep 14 2007 - 02:45:55 EDT