cocoon-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Marc Driftmeyer <mdr...@yahoo.com>
Subject Re: [poll] Java 5 as minimum requirement for Cocoon 2.2
Date Wed, 23 Aug 2006 04:57:17 GMT
Just an observation, but isn't 2.2 a redesign from 2.1.x branch that
significantly restructured Cocoon (Maven, CForms, XSP deprecated, etc)?

2.1.x is legacy as 1.8.x is now legacy. 2.2 would be current and
2.3/3.0 development/experimental.

Debian has 4 Branches. At least if all possible their should be a
Sid/Unstable branch that isn't Experimental and isn't Stable for Cocoon
that would allow us to use most of the modern features in Java 5, let
alone Java 6 when it rolls out from Beta and Release Candidate
statuses.

What still seems to be dead in the water is Documentation and I mean
documentation that reminds one of the Cocoon Developer Handbook by
Moczar/Aston.

I recall about 9 months ago that this was a priority. From the Cocoon
site I don't see it has reached fruition. I see a lot of documentation
fractured across the Net via various wikis and other individual sites
but I don't see a repository of Documentation that one can funnel that
provides these practical/best practices, hands-on tutorials that were
envisioned.

Correct me if I'm wrong.

- Marc

--- Grzegorz Kossakowski <grek@tuffmail.com> wrote:

> Marc Driftmeyer napisał(a):
> > If Banking Institutions are the reason then we should fork the tree
> to
> > have two branches ala Firefox.
> >
> > One that targets legacy systems and the other for moving the system
> > forward.
> >   
> There are already two branches! One "2.1.x" and another "trunk". When
> we 
> C2.2 is out, then we have three branches: 2.1.x, 2.2.x, trunk. Trunk 
> would be used as line for 2.3/3.0 development, there would go stuff
> like 
> OSGi. 2.1.x branch would be maintain only for critical bugs and fixes
> 
> but it is what should banking institutions expect. Now, being stuck
> with 
> Java 1.4 they do not expect it to support annotations in the future.
> Why 
> they should not go for the same when it comes to Cocoon?
> 
> -- 
> Grzegorz Kossakowski
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
> For additional commands, e-mail: users-help@cocoon.apache.org
> 
> 


__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org


Mime
View raw message