Re: [2.1] Future of Cocoon 2.1.x... again :)
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. Regards, Cédric 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
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/
RE: [2.1] Future of Cocoon 2.1.x... again :)
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 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/
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. Thanks! *From:*Francesco Chicchiriccò [mailto:ilgro...@apache.org] *Sent:* Monday, December 12, 2011 11:22 AM *To:* 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 Robby 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/
RE: [2.1] Future of Cocoon 2.1.x... again :)
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: Requirements 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, Robby From: Francesco Chicchiriccò [mailto:ilgro...@apache.org] Sent: Monday, December 12, 2011 11:27 AM To: dev@cocoon.apache.org 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. Thanks! From: Francesco Chicchiriccò [mailto:ilgro...@apache.org] Sent: Monday, December 12, 2011 11:22 AM To: dev@cocoon.apache.orgmailto: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 Robby 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/
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 Subject: Re: [2.1] Future of Cocoon 2.1.x... again :) On 12/12/2011 11:00, Cdric 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, Cdric 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, Cdric [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/ -- www.anyware-services.com Inscrivez-vous notre newsletter Cdric Damioli Directeur technique cedric.dami...@anyware-services.com Tel : +33(0)5 6
Re: [2.1] Future of Cocoon 2.1.x... again :)
Hi Francesco, Indeed, if I run tests with a JDK 6, I also have JUnit failures (could not remember which ones) but IIRC all tests run fine with JDK 1.4 Cdric Le 12/12/2011 11:22, Francesco Chicchiricc a crit: On 12/12/2011 11:00, Cdric 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, Cdric 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, Cdric [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/ -- www.anyware-services.com Inscrivez-vous notre newsletter Cdric Damioli Directeur technique 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 www.ametys.org Ce message et toutes les pices jointes (le "Message") sont confidentiels et tablis l'intention exclusive de ses destinataires. Toute modification,
RE: [2.1] Future of Cocoon 2.1.x... again :)
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.orgmailto: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.comhttp://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/eyrpkhttp://eepurl.com/eyrpk Inscrivez-vous à notre newsletterhttp://eepurl.com/eyrpk Cédric Damioli Directeur technique cedric.dami...@anyware-services.commailto: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.orgwww.ametys.orghttp://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
Re: [2.1] Future of Cocoon 2.1.x... again :)
On Thu, 2011-08-11 at 15:54 +0200, Alec Bickerton wrote: First question I have to ask is whether there is anyone with the relevant permission to do anything with these patches. Every committer can write to c2.1. I somebody has rights to commit to c3 then he has for all of cocoon. salu2 Alec, On 11/08/11 15:36, Cédric Damioli wrote: 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 -- Thorsten Scherler thorsten.at.apache.org codeBusters S.L. - web based systems consulting, training and solutions http://www.codebusters.es/
Re: [2.1] Future of Cocoon 2.1.x... again :)
On Thu, 2011-08-11 at 17:56 +0200, Francesco Chicchiriccò wrote: On 11/08/2011 15:36, Cédric Damioli wrote: 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 ? Hi Cédric, some of my e-mails are part of your thread [1], and here I come again :-) In the meanwhile we dismissed our Cocoon 2.1 applications and we are moving everything to Cocoon 3: even though not mature, looks more promising, Anyway, I am not that familiar with C2.1 ant-based build process, so I don't think I can help you at all. Actually I do not see much issues regarding the ant build. Actually it is pretty much straight forward to build c2. ./build.sh; ./cocoon.sh We (the committer) should find the time to review this patches and apply them if working. To maintain our c2.1 user will benefit us as soon the first c3 apps are going into production and people see that it is worth into upgrading to c3. salu2 Devs, is there anyone still familiar with C2.1 build? Regards. [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 -- Thorsten Scherler thorsten.at.apache.org codeBusters S.L. - web based systems consulting, training and solutions http://www.codebusters.es/
Re: [2.1] Future of Cocoon 2.1.x... again :)
On 16/08/2011 10:37, Thorsten Scherler wrote: On Thu, 2011-08-11 at 17:56 +0200, Francesco Chicchiriccò wrote: On 11/08/2011 15:36, Cédric Damioli wrote: 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 ? Hi Cédric, some of my e-mails are part of your thread [1], and here I come again :-) In the meanwhile we dismissed our Cocoon 2.1 applications and we are moving everything to Cocoon 3: even though not mature, looks more promising, Anyway, I am not that familiar with C2.1 ant-based build process, so I don't think I can help you at all. Actually I do not see much issues regarding the ant build. Actually it is pretty much straight forward to build c2. ./build.sh; ./cocoon.sh We (the committer) should find the time to review this patches and apply them if working. To maintain our c2.1 user will benefit us as soon the first c3 apps are going into production and people see that it is worth into upgrading to c3. I totally agree but... how is the ant build organized? Are there (unit) tests? How can we be sure that the applied patched don't break other functionalities? The above procedure ./build.sh; ./cocoon.sh can only ensure that the code compiles, not much more :-) Is there any document for applying patches to C2.1.X branch? Or any kind of tests that can be run against the modified source code? C2.1 is in production in many places so the risk to make a complete mess for our C2.1 users is considerable, isn't it? Regards. Devs, is there anyone still familiar with C2.1 build? Regards. [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/
Re: [2.1] Future of Cocoon 2.1.x... again :)
On 16/08/2011 10:46, Francesco Chicchiriccò wrote: On 16/08/2011 10:37, Thorsten Scherler wrote: On Thu, 2011-08-11 at 17:56 +0200, Francesco Chicchiriccò wrote: On 11/08/2011 15:36, Cédric Damioli wrote: 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 ? Hi Cédric, some of my e-mails are part of your thread [1], and here I come again :-) In the meanwhile we dismissed our Cocoon 2.1 applications and we are moving everything to Cocoon 3: even though not mature, looks more promising, Anyway, I am not that familiar with C2.1 ant-based build process, so I don't think I can help you at all. Actually I do not see much issues regarding the ant build. Actually it is pretty much straight forward to build c2. ./build.sh; ./cocoon.sh We (the committer) should find the time to review this patches and apply them if working. To maintain our c2.1 user will benefit us as soon the first c3 apps are going into production and people see that it is worth into upgrading to c3. I totally agree but... how is the ant build organized? Are there (unit) tests? How can we be sure that the applied patched don't break other functionalities? The above procedure ./build.sh; ./cocoon.sh can only ensure that the code compiles, not much more :-) Is there any document for applying patches to C2.1.X branch? Or any kind of tests that can be run against the modified source code? C2.1 is in production in many places so the risk to make a complete mess for our C2.1 users is considerable, isn't it? 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? Devs, is there anyone still familiar with C2.1 build? Regards. [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/
Re: [2.1] Future of Cocoon 2.1.x... again :)
First question I have to ask is whether there is anyone with the relevant permission to do anything with these patches. Alec, On 11/08/11 15:36, Cédric Damioli wrote: 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
Re: [2.1] Future of Cocoon 2.1.x... again :)
On 11/08/2011 15:36, Cédric Damioli wrote: 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 ? Hi Cédric, some of my e-mails are part of your thread [1], and here I come again :-) In the meanwhile we dismissed our Cocoon 2.1 applications and we are moving everything to Cocoon 3: even though not mature, looks more promising, Anyway, I am not that familiar with C2.1 ant-based build process, so I don't think I can help you at all. Devs, is there anyone still familiar with C2.1 build? Regards. [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/
