Like Chris, I never could adapt to the build and Spring changes in
Cocoon 2.2, and continued (until a few years ago) to develop projects
from Cocoon 2.1 (v2.1.13). I love and am still passionate about the
original 2.1 framework, having used it since 2002. In fact, I would
still be using it if not for security, and other, challenges with the
old code.
The thing that drew me to Cocoon in the first place was the terrific
pipeline transformer architecture: it really fit the text transforming
ability of XSLT. It is something I greatly miss in Python.
I like the idea of using GitHub (https://github.com/apache/cocoon), as
it may expose more people to the project. In this regard, explaining
what Cocoon does, benefits of using it etc., might attract some passers by.
Thank you to all of you, who have, over the years, contributed and
participated in this beautiful piece of software.
Dan
===========
On 2023-11-21 6:46 a.m., Peter Hunsberger wrote:
On Tue, Nov 21, 2023 at 12:15 AM Christofer Dutz
<christofer.d...@c-ware.de> wrote:
Well guess I haven't stated it yet: I would be willing to work on
it (I've especially for some ideas on streaming industrial data
from plc4x).
Personally I would let the pre-2.2 branch rest in peace. All is
dependencies are so extremely old and the jdks for some are no
longer available. At least I probably wouldn't touch it and focus
on the "middle"...
+1 !
Possibly have a look at 3.0 (haven't done that yet).
I tried using 3.0 for a project. Some good ideas and simple enough
implementation but I don't think there is enough there for it to be
worth saving....
Chris
Gesendet von Outlook für Android <https://aka.ms/AAb9ysg>
------------------------------------------------------------------------
*From:* Cédric Damioli <cdami...@apache.org>
*Sent:* Monday, November 20, 2023 3:47:14 PM
*To:* dev@cocoon.apache.org <dev@cocoon.apache.org>
*Subject:* Re: Now that the release is out, what's next?
Hi,
On top of that, as a community, we now have to formally answer to
the below question (going or not to the Attic) not only once, but
three times, one time for each subproject we still officially
maintain since more than 10 years :
- Cocoon 2.1.x (pre-Spring, pre-Maven). Last release 2.1.13 was
rolled out 3 years ago.
- Cocoon 2.2x (now 2.3.x). Last release these days.
- Cocoon 3.0.x. Last release 3.0.0-alpha-3 back in 2011
Those 3 versions are not compatible with each other, are not meant
as drop-in replacements, and have evolved differently over the years.
The community could either decide to stop the project as-is and go
to the Attic, or start over maintaining only one or two branches.
Cédric
Le 19/11/2023 à 18:20, Christofer Dutz a écrit :
Hi folks,
So, it seems that we finally have finished the last missing steps
to formally get the release out the door. Now I think comes a
time where we should reflect and discuss, what should happen with
the Project.
So instead of simply saying: Releasing it was such a struggle
(not technically, but from a participation side) I wouldn’t say
this project is healthy and we should discuss a move into the Attic.
However, I could also imagine that the changes I implemented in
the build might encourage some folks to give it another go.
I know when I was doing projects with Cocoon as part of my
day-job 20 years ago, Cocoon 2.2 sort of completely broke my
flow. Not only my inexperience with Maven, but also that of
Spring and the versioning scheme where all sorts of cocoon
modules had different versions just made me give up at that time
and switch to Adobe Flex ;-)
Now (15 years later) Maven and Spring have evolved and with the
cleanups in the build, it should be a lot simpler to work with
Cocoon and with all modules sharing the same version, also this
should be a lot simpler.
So, I would like to ask you folks:
* Should we aim directly for the Attic?
* Does anyone want to revive the project? (I’m intentionally
not only addressing committers and PMC members, but also
people wanting to keep the project alive)
Chris
--
Cédric Damioli
CMS - Java - Open Source
www.ametys.org <http://www.ametys.org>
