--- Joerg Heinicke <[EMAIL PROTECTED]> schrieb:
> On 17.08.2005 11:22, Andrew Stevens wrote:
>
> > Although as a mere user my vote probably doesn't
> count,
>
> It's a so-called non-binding vote, but your opinion
> is important though.
>
> > from my
> > perspective I'm extremely grateful that Cocoon
> still supports 1.3 and
> > hope that remains the case for the 2.1.x releases.
> Our production
> > servers are running Websphere 5.0.x, which only
> has JDK 1.3.1, and
> > aren't likely to upgrade in the short term (a
> combination of internal
> > bureaucracy and the amount of testing involved for
> all the other apps
> > running on those servers). So if 2.1.8 drops
> support for 1.3, I'll
> > probably have to stick at 2.1.7 for our team's
> app; either that or drop
> > Cocoon altogether and migrate to the "company
> standard" (proprietary)
> > framework, which I've managed to hold out against
> up till now ;-)
> >
> > Besides, wouldn't something like that justify a
> bigger change in version
> > number i.e. if you're going to drop it, do it in
> 2.2?
>
> Yes, definitely. Such an important incompatibility
> would need a minor
> version number update IMO instead of just on the
> patch level. The change
> to Java 1.4 was already decided for Cocoon 2.2. I
> would not like to see
> Java 1.3 support been dropped for Cocoon 2.1.x. If
> it is just an issue
> for the library update we simply don't need to
> update each library to
> each version.
>
> Joerg
I fully agree with you Jörg. If we make JDK 1.4 a
requirement for Cocoon, then the next version should
be 2.2 and not 2.1.8.
--
Reinhard
___________________________________________________________
Gesendet von Yahoo! Mail - Jetzt mit 1GB Speicher kostenlos - Hier anmelden:
http://mail.yahoo.de
