Cocoon 2.1.11 should be working with any JVM 1.3 and up. Because nobody is actually using 1.3 anymore for development, there were several occasions that library features not available in 1.3 crept in. Therefore it was decided that the next release 2.1.12 should require 1.4. I would not recommend actually using 1.3 or 1.4 anymore because of its non-existent memory model.
Cheers, Alfred. From: Cédric Damioli [mailto:cedric.dami...@anyware-services.com] Sent: Montag, 12. Dezember 2011 11:37 To: dev@cocoon.apache.org Subject: Re: [2.1] Future of Cocoon 2.1.x... again :) Cocoon 2.1.x was meant to be used with 1.3 But the release notes file of the current 2.1.12-dev mention 1.4 as minimum requirement ! Le 12/12/2011 11:24, Robby Pelssers a écrit : What JDK are you using? It seems like you will need a very old JDK for this branch to work. Robby From: Francesco Chicchiriccò [mailto:ilgro...@apache.org] Sent: Monday, December 12, 2011 11:22 AM To: dev@cocoon.apache.org<mailto:dev@cocoon.apache.org> 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 : https://issues.apache.org/jira/browse/COCOON-2319 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 https://svn.apache.org/repos/asf/cocoon/branches/BRANCH_2_1_X cocoon-2_1_X 2. cp blocks.properties local.blocks.properties 3. set include.all.blocks=true 4. ./build.sh 5. ./build.sh test resulted in 6 test failures (DefaultRunnableManagerTestCase) Am I doing something wrong? [8] http://mail-archives.apache.org/mod_mbox/cocoon-dev/201108.mbox/%3c4e4a7273.2020...@apache.org%3E 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, Cédric [1] http://markmail.org/thread/hizllvbjdeurr2de [2] https://issues.apache.org/jira/browse/COCOON-2288, allow to use SLF4J [3] https://issues.apache.org/jira/browse/COCOON-2307, bug in the ResourceReader [4] https://issues.apache.org/jira/browse/COCOON-2309, possible bug with SitemapSource under certain circumstances [5] https://issues.apache.org/jira/browse/COCOON-2310, XHTMLSerializer from serializers block does not handle HTML5 [6] https://issues.apache.org/jira/browse/COCOON-2313, subclassing of org.apache.cocoon.Cocoon [7] https://issues.apache.org/jira/browse/COCOON-2314, override upload params in CocoonServlet -- Francesco Chicchiriccò Apache Cocoon Committer and PMC Member http://people.apache.org/~ilgrosso/<http://people.apache.org/%7Eilgrosso/> -- [cid:image001.png@01CCB8DC.9D3BF550]<http://www.anyware-services.com> www.anyware-services.com<http://www.anyware-services.com> [cid:image002.png@01CCB8DC.9D3BF550]<http://www.twitter.com/anywareservices>[cid:image003.png@01CCB8DC.9D3BF550]<http://www.facebook.com/AnywareServices>[cid:image004.png@01CCB8DC.9D3BF550]<http://eepurl.com/eyrpk><http://eepurl.com/eyrpk> Inscrivez-vous à notre newsletter<http://eepurl.com/eyrpk> Cédric Damioli Directeur technique cedric.dami...@anyware-services.com<mailto:cedric.dami...@anyware-services.com> Tel : +33(0)5 62 19 19 07 Mob : +33(0)6 87 03 61 63 Fax : +33(0)5 61 75 84 12 Adresse : Innopole 13 - 254 avenue de l'Occitane - B.P 97672 - 31676 LABEGE CEDEX - France Ametys: Smart Web CMS [cid:image005.gif@01CCB8DC.9D3BF550]<http://www.ametys.org>www.ametys.org<http://www.ametys.org> Ce message et toutes les pièces jointes (le "Message") sont confidentiels et établis à l'intention exclusive de ses destinataires. Toute modification, édition, utilisation ou diffusion non autorisée est interdite. Anyware Services décline toute responsabilité au titre de ce Message s'il a été altéré, déformé, falsifié ou édité, diffusé sans autorisation. The content of this e-mail is intended only for the confidential use of the person addressed. If you are not the intended recipient, please notify the sender and delete this e-mail immediately. Thank you.
<<inline: image001.png>>
<<inline: image002.png>>
<<inline: image003.png>>
<<inline: image004.png>>
<<inline: image005.gif>>
