cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Robby Pelssers <>
Subject RE: [2.1] Future of Cocoon 2.1.x... again :)
Date Mon, 12 Dec 2011 10:32:01 GMT
Just saying that in a previous problem with 2.1.9 they were mentioning JDK1.4 (still giving
issues) and JDK1.3 running fine. Hence my remark.   Although I worked with really old versions
of Cocoon I don't know what the installation / build  requirements are.

I found this in the readme.txt for 2.1.9:


  Cocoon has been designed to coexist and interoperate side-by-side with your
  existing J2EE solutions or to give them new functionality without requiring
  any change in the existing infrastructure.

  Cocoon is implemented both as a Java servlet and a Java command line
  application. The following requirements exist for installing it:

   o  A Java 1.3 or later compatible virtual machine for your operating system.

   o  A Servlet API 2.2 compatible Servlet Engine or J2EE Application Server.
      [not required for command line operation]

Kind regards,
From: Francesco Chicchiriccò []
Sent: Monday, December 12, 2011 11:27 AM
Subject: Re: [2.1] Future of Cocoon 2.1.x... again :)

On 12/12/2011 11:24, Robby Pelssers wrote:
What JDK are you using?  It seems like you will need a very old JDK for this branch to work.

Hum, nice spot :-)
I remember that last time I run C2.1 I was on JDK 1.5, but I probably ran the tests below
with latest JDK 6: I'll give a try ASAP with latest 1.5 downloadable from Oracle website.


From: Francesco Chicchiriccò []
Sent: Monday, December 12, 2011 11:22 AM
Subject: Re: [2.1] Future of Cocoon 2.1.x... again :)

On 12/12/2011 11:00, Cédric Damioli wrote:
Hi team,

I recently came again across annoying 2.1 bugs, which I have proposed patches for, and realized
that I received almost no answers to my "what's the future of Cocoon 2.1" e-mail, and that
my patches have not been reviewed nor committed.
I have found and patched a new one this morning :

As I previously said, I fully understand that current Cocoon committers are focused on Cocoon
3, and that they probably have no great interest to old maintenance releases.
Again, I totally volunteer to help to maintain and release 2.1.x branch, as I have dozens
of production applications on top of it, running with a a-lot-patched Cocoon.
Please tell me what I can do to help.

Hi Cedric,
as I wrote in [8], here it follows what I did for building C2.1 trunk (in order to start applying
your patches, of course):

1. svn co cocoon-2_1_X
2. cp
3. set include.all.blocks=true
4. ./
5. ./ test

resulted in 6 test failures (DefaultRunnableManagerTestCase)

Am I doing something wrong?


Le 11/08/2011 15:36, Cédric Damioli a écrit :

Hi Cocoon team,

A little more than one year ago, I sent a mail [1] to this list, to get feedbacks about usage
of Cocoon 2.1.x, 3 years after the last release.
I must admit that I received many more answers (privately and publicly on the list) than I
could have expected first.
This proved me the vitality of the 2.1.x community.
So I began to open some tickets [2] [3] [4] [5] [6] [7] and provide some patches gathered
during the last years on my projects, but unfortunately, I received nearly no feedback from
committers around here.
Is there still any interest from devs for the 2.1.x branch ?
Could someone review the patches ? I obviously volunteer to help, to stop having to run dozen
apps with a patched Cocoon.
Has someone interest to prepare and schedule a 2.1.12 maintenance release ?

Best regards,

[2], allow to use SLF4J
[3], bug in the ResourceReader
[4], possible bug with SitemapSource under
certain circumstances
[5], XHTMLSerializer from serializers block
does not handle HTML5
[6], subclassing of org.apache.cocoon.Cocoon
[7], override upload params in CocoonServlet


Francesco Chicchiriccò

Apache Cocoon Committer and PMC Member

View raw message