2.12 Release: Additions to COCOON-2333 (list of current jars)

[insigh...@gmail.com]

Here are some additions to COCOON-2333 (list of current jar files). I'm 
also attaching a .txt file in case that's easier to use.


Is the plan to upgrade the code to use the newer jar versions for the 
2.12 release?


Thanks,

Dan

==

Additions to:
https://svn.apache.org/viewvc/cocoon/branches/BRANCH_2_1_X/misc/notes/review-jars.txt?view=markup

Issue: COCOON-2333

Notes: I'm not a developer so functionality/compatibility with cocoon 
may not work!




148 L: lib/optional/batik-all-1.6.jar
149 F: C:
150 R: batik-1.7;  batik-src-1.7.zip OR batik-1.7.zip
151 http://xmlgraphics.apache.org/batik/



161 L: lib/optional/chaperon-20040205.jar
162 F: C:
163 R: chaperon-3.0;  chaperon-3.0-final-src.tar.gz OR 
chaperon-3.0-final-bin.tar.gz

http://chaperon.sourceforge.net/



169 L: lib/optional/commons-codec-1.3.jar
170 F: C:
171 R: commons-codec-1.7;  commons-codec-1.7-bin.tar.gz  OR 
commons-codec-1.7-src.tar.gz

https://commons.apache.org/codec/



218  L: lib/optional/fop-0.95.jar
219  F: C:
220  R: fop-1,1; fop-1.1-src.tar.gz OR fop-1.1-bin.tar.gz
https://xmlgraphics.apache.org/fop/1.1/



247 L: lib/optional/icu4j-2.8.jar
248 F: X:
249 R: icu4j-50_1; icu4j-50_1.tgz, icu4j-charset-50_1.jar, 
icu4j-localespi-50_1.jar

https://ssl.icu-project.org/icu-jsp/downloadPage.jsp?ver=50.1&base=j&svn=release-50-1
http://site.icu-project.org/



251 L: lib/optional/itext-1.1.jar
252 F: X:
253 R: itext-5.3.4; itext-5.3.4.zip
http://itextpdf.com/, 
http://sourceforge.net/projects/itext/files/iText/iText5.3.4/




299 L: lib/optional/jtidy-04aug2000r7-dev.jar
300 F: C:
301 R: jtidy-r938; jtidy-r938.zip OR jtidy-r938-sources.zip
http://jtidy.sourceforge.net/ 
(http://sourceforge.net/projects/jtidy/files/JTidy/r938/)




303 L: lib/optional/lucene-1.4.3.jar
304 F: C:
305 R: lucene-4.0.0;  lucene-4.0.0-src.tgz OR lucene-4.0.0.tgz
https://lucene.apache.org/
See also the SOLR Project (https://lucene.apache.org/solr/, now v4)



317 L: lib/optional/nekohtml-0.9.5.jar
318 F: X:
319 R: nekohtml-1.9.17;  nekohtml-1.9.17.tar.gz OR nekohtml-1.9.17.zip
http://nekohtml.sourceforge.net/



329 L: lib/optional/poi-3.0.2-FINAL-20080204.jar
330 F: X:
331 R: poi-3.9;  poi-bin-3.9-20121203.tar.gz  OR 
poi-src-3.9-20121203.tar.gz

https://poi.apache.org/
Notes: See also, alternative TIKA Project (tika.apache.org); Current 
SOLR v4 distro uses poi-3.8.jar, poi-ooxml-3.8.jar, 
poi-ooxml-schemas-3.8.jar and poi-scratchpad-3.8.jar




365 L: lib/optional/velocity-1.4.jar
366 F: X:
367 R: velocity-1.7;  velocity-1.7.tar.gz
https://velocity.apache.org/



393 L: lib/optional/xmlgraphics-commons-1.3.1.jar
394 F: C:
395 R: xmlgraphics-commons-1.5; xmlgraphics-commons-1.5-bin.tar.gz 
OR xmlgraphics-commons-1.5-src.tar.gz

https://xmlgraphics.apache.org/commons/
Additions to:
https://svn.apache.org/viewvc/cocoon/branches/BRANCH_2_1_X/misc/notes/review-jars.txt?view=markup
Issue: COCOON-2333

Notes: I'm not a developer so functionality/compatibility with cocoon may not 
work!



148 L: lib/optional/batik-all-1.6.jar
149 F: C:
150 R: batik-1.7;  batik-src-1.7.zip OR batik-1.7.zip
151 http://xmlgraphics.apache.org/batik/



161 L: lib/optional/chaperon-20040205.jar
162 F: C:
163 R: chaperon-3.0;  chaperon-3.0-final-src.tar.gz OR 
chaperon-3.0-final-bin.tar.gz
http://chaperon.sourceforge.net/



169 L: lib/optional/commons-codec-1.3.jar
170 F: C:
171 R: commons-codec-1.7;  commons-codec-1.7-bin.tar.gz  OR  
commons-codec-1.7-src.tar.gz
https://commons.apache.org/codec/



218  L: lib/optional/fop-0.95.jar
219  F: C:
220  R: fop-1,1; fop-1.1-src.tar.gz OR fop-1.1-bin.tar.gz
https://xmlgraphics.apache.org/fop/1.1/



247 L: lib/optional/icu4j-2.8.jar
248 F: X:
249 R: icu4j-50_1; icu4j-50_1.tgz, icu4j-charset-50_1.jar, 
icu4j-localespi-50_1.jar
https://ssl.icu-project.org/icu-jsp/downloadPage.jsp?ver=50.1&base=j&svn=release-50-1
http://site.icu-project.org/



251 L: lib/optional/itext-1.1.jar
252 F: X:
253 R: itext-5.3.4; itext-5.3.4.zip
http://itextpdf.com/, 
http://sourceforge.net/projects/itext/files/iText/iText5.3.4/



299 L: lib/optional/jtidy-04aug2000r7-dev.jar
300 F: C:
301 R: jtidy-r938; jtidy-r938.zip OR jtidy-r938-sources.zip
http://jtidy.sourceforge.net/ 
(http://sourceforge.net/projects/jtidy/files/JTidy/r938/)



303 L: lib/optional/lucene-1.4.3.jar
304 F: C:
305 R: lucene-4.0.0;  lucene-4.0.0-src.tgz OR lucene-4.0.0.tgz
https://lucene.apache.org/
See also the SOLR Project (https://lucene.apache.org/solr/, now v4)



317 L: lib/optional/nekohtml-0.9.5.jar
318 F: X:
319 R: nekohtml-1.9.17;  nekohtml-1.9.17.tar.gz OR nekohtml-1.9.17.zip
http://nekohtml.sourceforge.net/



329 L: lib/optional/poi-3.0.2-FINAL-20080204.jar
330 F: X:
331 R: poi-3.9;  poi-bin-3.9-20121203.tar.gz  OR poi-src-

Re: 2.12 Release: Additions to COCOON-2333 (list of current jars)

[insigh...@gmail.com]

Was looking through the list of 2.1.12 jars, and notice that many of the 
jars are quite old.


https://svn.apache.org/viewvc/cocoon/branches/BRANCH_2_1_X/misc/notes/review-jars.txt?view=markup

I also notice that my additions (sent 11 Dec) are not included.

What are the plans to upgrade the jars before the 2.1.12 release?

Thanks,

Dan

Re: 2.12 Release: Additions to COCOON-2333 (list of current jars)

[insigh...@gmail.com]

On 2013-01-21 9:40 PM, David Crossley wrote:

Francesco Chicchiriccò wrote:

insigh...@gmail.com wrote:

Was looking through the list of 2.1.12 jars, and notice that many of
the jars are quite old.

https://svn.apache.org/viewvc/cocoon/branches/BRANCH_2_1_X/misc/notes/review-jars.txt?view=markup

I also notice that my additions (sent 11 Dec) are not included.


As explained by various people, the Java version limitation
must remain. I re-reviewed the list at that time, changed the
format of the notes, and noted the maximum version available
for some of the dependencies.


Thanks David (and all the devs who are working hard to release 2.1.12) 
-- I see you did add some of my additions to the list, and apologize for 
missing those.


I also appreciate the need for supporting legacy systems, and look 
forward to continuing to incorporate newer jars and JDKs in the future.


Dan

Re: [VOTE] Apache Cocoon 2.3.0 RC1

[insigh...@gmail.com]

Great work everyone on the Cocoon updates. To that end, was wondering if 
you are aware of the updates DSpace.org team/users did to their own 
Cocoon 2.2 architecture?


DSpace v6 was the major version using Cocoon 2.2 (they have since moved 
to Angular JS)


Might be worth a look to see if some of that work can be ported into 2.3?

Dan


On 2023-10-24 12:50 p.m., Christofer Dutz wrote:


Apache Cocoon 2.3.0 has been staged under [2] and it’s time to vote

on accepting it for release. All Maven artifacts are available under [1].

Voting will be open for 72hr.

A minimum of 3 binding +1 votes and more binding +1 than binding -1

are required to pass.

Release tag: 
https://svn.apache.org/viewvc/cocoon/tags/cocoon-2.3/cocoon/cocoon-2.3.0/


Director revision of the tag: 1913280

Per [3] "Before voting +1 PMC members are required to download

the signed source code package, compile it as provided, and test

the resulting executable on their own platform, along with also

verifying that the package meets the requirements of the ASF policy

on releases."

You can achieve the above by following the guide of a fellow Apache 
project [4].


[ ]  +1 accept (indicate what you validated - e.g. performed the 
non-RM items in [4])


[ ]  -1 reject (explanation required)

[1] 
https://repository.apache.org/content/repositories/orgapachecocoon-1006 



[2] https://dist.apache.org/repos/dist/dev/cocoon/2.3.0/rc1/ 



[3] https://www.apache.org/dev/release.html#approving-a-release 



[4] 
https://cwiki.apache.org/confluence/display/PLC4X/Validating+a+staged+Release 

Re: Now that the release is out, what's next?

[insigh...@gmail.com]

I mentioned this early, the DSpace Content Management project used 
Cocoon 2.2 until version 6.4 (v7 moved to Angular JS). They integrated 
with Solr and did a bunch of other things that may be worth a look.


The Cocoon interface was called xmlui (look for the subfolder), and 
available via Github:


https://github.com/DSpace/DSpace/releases

Source Code: 
https://github.com/DSpace/DSpace/archive/refs/tags/dspace-6.4.tar.gz


Great work on continuing the Cocoon legacy!

Dan


On 2023-11-19 10:20 a.m., Christofer Dutz wrote:


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

Re: Now that the release is out, what's next?

[insigh...@gmail.com]

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 
 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 

*From:* Cédric Damioli 
*Sent:* Monday, November 20, 2023 3:47:14 PM
*To:* 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  

Re: AW: [RESULT] [VOTE] Move Apache Cocoon into the Apache Attic

[insigh...@gmail.com]

Dspace (prior to version 7) used Cocoon 2.2, and enhanced its 
functionality, for instance, integration with Lucene SOLR. Look for the 
XMLUI section available from:


https://github.com/DSpace/DSpace/releases/tag/dspace-6.4

Release Notes:

https://wiki.lyrasis.org/display/DSDOC6x

I always continued to use Cocoon version 2.1x, and am hoping to use LLMs 
to help me refactor some of its code. I am not a JAVA developer. There 
were a few old code samples many (many years) ago adding some java 
classes, which I believe were never fully integrated into 2.13.


I still love 2.1x, and would like to see better html parser cleanup than 
jsoup/niko, hardening security issues, and wow, if the python integrator 
package could ever be upgraded, that would tie in nicely with the wide 
use of python language.


Cocoon pipelines are awesome.

Dan




On 2024-09-13 8:15 a.m., Cédric Damioli wrote:

Do you think there exist "multiple" forks ?
I'm now aware of Gabriel's but are there any others ?

Cédric

Le 13/09/2024 à 15:58, Christofer Dutz a écrit :


It does seem as if multiple people claimed to still be using Cocoon, 
but maintaining their own forks.


Why not bring exactly this back to the upstream project and join 
forces in maintaining it?


Chris

*Von: *Cédric Damioli 
*Datum: *Donnerstag, 12. September 2024 um 19:31
*An: *dev@cocoon.apache.org 
*Betreff: *Re: [RESULT] [VOTE] Move Apache Cocoon into the Apache Attic

Hi,

Sadly, there's not enough motivated individuals to keep the project 
running as is.
When we ran a poll 10 months ago, very few people actually 
volunteered to help keeping Cocoon 2.3 alive, and the reality of 
these past 10 months is that nobody has barely done anything to move 
forward.


Anyway, now that the Attic vote has passed, we have to move forward 
with the due process.


Cédric

Le 11/09/2024 à 13:27, Gabriel Gruber a écrit :

>> Can you explain why you didn't via
https://github.com/apache/cocoon ?

Hmm, good question actually. I wasn’t aware that the PR
functionality was actually really used to add enhancements to the
project and I always felt a little bit lost with the
formal/administrative rules to get patches to the project,
without being an official committer.

Anyway I would be willing to add all necessary changes to make
cocoon compatible with spring 5+ in a PR

Cheerio,

Gabriel

*From: *Torsten Curdt  
*Date: *Wednesday, 11. September 2024 at 10:59
*To: *dev@cocoon.apache.org 

*Subject: *Re: [RESULT] [VOTE] Move Apache Cocoon into the Apache
Attic

It is sad, to let such a powerful project die. Having said
that, we are using it still in production and trying to apply
security patches on our own fork to make it compatible with
newer versions of spring and java.

If the project would continue on github, I can just stress
again that I would be very happy to participate and share all
our patches.


Can you explain why you didn't via https://github.com/apache/cocoon ?

Just trying to understand whether github would really make a
difference.

While I am still +1 for the attic (because I don't see anyone
working on Cocoon in any form),
it feels a little sad if there are individually maintained forks
that could as well be part of the project.

cheers,
Torsten