kedar mhaswade wrote:
> नमस्ते! (It is "Salut" in Samskritam :))
>
> But then wouldn't it mean we can't use JDK-6 specific API/implementation?
>
> I agree, there is a maintenance overhead here.
>
> Although I fully understand supporting JDK5, shouldn't we encourage
> users to upgrade to JDK6 soon?
>
How do you do that? It's clear that GlassFish v3 next will only run on
JDK 6 and later, because of the Java EE
spec alignment issue. But customers take a VERY long time to migrate to
the latest JDK. JDK 5 won't even
be EOL'd until October this year. Maintaining a separate branch for JDK
6 is too much overhead.
I'd hate to impact Grizzly community adoption just for the sake of
moving to JDK 6.
We MIGHT consider moving to JDK 6 as the minimum for Grizzly 2.0, which
will probably be in
GlassFish v3.next.next release (why can't we construct a roadmap with
sensible release designations :-( ? )
Ken.