Francesco Chicchiriccò | 8 Jun 12:08 2011
Picon

[C3] Fwd: [Hippo-cms7-user] Cocoon 3 based frontend

Hi there,
fist of all, sorry for the cross-posting.

You can find below an e-mail that I've just sent to the Hippo CMS mailing list.
There is some concrete possibility to use Cocoon 3 in a (rather small, as said) production environment.

I would basically like to build a JCR SAX transformer (similar in functions to the Cocoon 2.1 WebDAV transformer) but I would also need, for example, some caching and i18n features.

Do you see any particular issues besides the obvious risk of using an Alpha-2 (not yet Alpha-3) software for production? ;-)

-------- Messaggio originale -------- Oggetto: Data: Mittente: Rispondi-a: Organizzazione: A:
[Hippo-cms7-user] Cocoon 3 based frontend
Wed, 08 Jun 2011 12:02:32 +0200
Francesco Chicchiriccò <francesco.chicchiricco <at> tirasa.net>
Hippo CMS 7 development public mailinglist <hippo-cms7-user <at> lists.onehippo.com>
Tirasa
Hippo CMS 7 development public mailinglist <hippo-cms7-user <at> lists.onehippo.com>


Hi all, we've recently got a (rather small, indeed) customer with a very particular need: to be able, in the near future, to migrate either all the documents from its current legacy CMS and also all of its Cocoon 2.1 sites. They basically want to preserve - as much as possible - past investments done in terms of XSLTs and components. We are now defining the basic structure of our project and we do want to put Hippo CMS 7.6 in place. Of course this would mean to replace all the HST2 stuff that is normally involved when building sites with some Cocoon-based components. Looking at the documentation, I've found this reference to the Hippo's JCR interface [1]. Do you think it would be fine to build something that will interact with Hippo repository at that level or instead there are some higher-level classes from HST2 that should instead taken into account? Do you have any particular advice when doing such operation? Is there any more documentation we should take a look at? Thanks. [1] http://www.onehippo.org/cms7/documentation/development/content+repository/jcr/index.html -- Dott. Francesco Chicchiriccò Tel +393290573276 Amministratore unico <at> Tirasa S.r.l. Viale D'Annunzio 267 - 65127 Pescara Tel +39 0859116307 / FAX +39 0859111173 http://www.tirasa.net Apache Cocoon Committer and PMC Member http://people.apache.org/~ilgrosso/ "To Iterate is Human, to Recurse, Divine" (James O. Coplien, Bell Labs) _______________________________________________ Hippo-cms7-user mailing list and forums http://www.onehippo.org/cms7/support/forums.html
Simone Tripodi | 8 Jun 18:42 2011
Picon

Re: [C3] Fwd: [Hippo-cms7-user] Cocoon 3 based frontend

Great achievement Francesco, congrats!!!

the good news is that starting from tomorrow morning I'll be on forced vacations for a looooong time and I have a lot of spare time to dedicate to OSS, so potentially starting from tomorrow morning we can have an Alpha3 release candidate!!!
So, if it would help, I'll start the release process paying much more care than the first attempt.
HTH, all the best!!!
Simo

http://people.apache.org/~simonetripodi/
http://www.99soft.org/


2011/6/8 Francesco Chicchiriccò <ilgrosso <at> apache.org>
Hi there,
fist of all, sorry for the cross-posting.

You can find below an e-mail that I've just sent to the Hippo CMS mailing list.
There is some concrete possibility to use Cocoon 3 in a (rather small, as said) production environment.

I would basically like to build a JCR SAX transformer (similar in functions to the Cocoon 2.1 WebDAV transformer) but I would also need, for example, some caching and i18n features.

Do you see any particular issues besides the obvious risk of using an Alpha-2 (not yet Alpha-3) software for production? ;-)

-------- Messaggio originale -------- Oggetto: Data: Mittente: Rispondi-a: Organizzazione: A:
[Hippo-cms7-user] Cocoon 3 based frontend
Wed, 08 Jun 2011 12:02:32 +0200
Francesco Chicchiriccò <francesco.chicchiricco <at> tirasa.net>
Hippo CMS 7 development public mailinglist <hippo-cms7-user <at> lists.onehippo.com>
Tirasa
Hippo CMS 7 development public mailinglist <hippo-cms7-user <at> lists.onehippo.com>


Hi all, we've recently got a (rather small, indeed) customer with a very particular need: to be able, in the near future, to migrate either all the documents from its current legacy CMS and also all of its Cocoon 2.1 sites. They basically want to preserve - as much as possible - past investments done in terms of XSLTs and components. We are now defining the basic structure of our project and we do want to put Hippo CMS 7.6 in place. Of course this would mean to replace all the HST2 stuff that is normally involved when building sites with some Cocoon-based components. Looking at the documentation, I've found this reference to the Hippo's JCR interface [1]. Do you think it would be fine to build something that will interact with Hippo repository at that level or instead there are some higher-level classes from HST2 that should instead taken into account? Do you have any particular advice when doing such operation? Is there any more documentation we should take a look at? Thanks. [1] http://www.onehippo.org/cms7/documentation/development/content+repository/jcr/index.html -- Dott. Francesco Chicchiriccò Tel +393290573276 Amministratore unico <at> Tirasa S.r.l. Viale D'Annunzio 267 - 65127 Pescara Tel +39 0859116307 / FAX +39 0859111173 http://www.tirasa.net Apache Cocoon Committer and PMC Member http://people.apache.org/~ilgrosso/ "To Iterate is Human, to Recurse, Divine" (James O. Coplien, Bell Labs) _______________________________________________ Hippo-cms7-user mailing list and forums http://www.onehippo.org/cms7/support/forums.html

Simone Tripodi | 8 Jun 21:16 2011
Picon

[C3] Release process clarification needed

Hi Reinhard/all,
can someone explain me please what the third point in the
RELEASE_HOWTO.txt means:

* set all versions in the generated pom.xml files of all archetypes

I didn't see where poms have been generated... thanks in advance!!!
Simo

http://people.apache.org/~simonetripodi/
http://www.99soft.org/

Reinhard Pötz | 8 Jun 22:04 2011
Picon

Re: [C3] Fwd: [Hippo-cms7-user] Cocoon 3 based frontend

On 06/08/2011 12:08 PM, Francesco Chicchiriccò wrote:
> Hi there,
> fist of all, sorry for the cross-posting.
>
> You can find below an e-mail that I've just sent to the Hippo CMS
> mailing list.
> There is some concrete possibility to use Cocoon 3 in a (rather small,
> as said) production environment.
>
> I would basically like to build a JCR SAX transformer (similar in
> functions to the Cocoon 2.1 WebDAV transformer) but I would also need,
> for example, some caching and i18n features.
>
> Do you see any particular issues besides the obvious risk of using an
> Alpha-2 (not yet Alpha-3) software for production? ;-)

No, not that I know of any than the mentioned ones.

Reinhard

--

-- 
Reinhard Pötz         Founder & Managing Director, Indoqa and Deepsearch
                         http://www.indoqa.com/people/reinhard-poetz.html

Member of the Apache Software Foundation
Apache Cocoon Committer, PMC member                  reinhard <at> apache.org
________________________________________________________________________

       Furthermore, I think Oracle has to honor the JSPA agreement.
     http://s.apache.org/JCPIsDead       http://s.apache.org/tck-trap

Reinhard Pötz | 8 Jun 23:19 2011
Picon

Re: [C3] Release process clarification needed

On 06/08/2011 09:16 PM, Simone Tripodi wrote:
> Hi Reinhard/all,
> can someone explain me please what the third point in the
> RELEASE_HOWTO.txt means:
>
> * set all versions in the generated pom.xml files of all archetypes
>
> I didn't see where poms have been generated... thanks in advance!!!

I've just updated the RELEASE_HOWTO.txt.

HTH

I also fixed the sample and the block archetype.

To make things clearer for cocoon-archetype-sample: the sample-archetype 
uses a Groovy script to generate the assembly descriptor on the fly 
based on the content of cocoon-sample and copies all relevant resources 
to src/main/resources/archetype-resources

Maybe there are better ways to achieve this goal with 'standard' Maven 
plugins in the meantime ...

--

-- 
Reinhard Pötz         Founder & Managing Director, Indoqa and Deepsearch
                         http://www.indoqa.com/people/reinhard-poetz.html

Member of the Apache Software Foundation
Apache Cocoon Committer, PMC member                  reinhard <at> apache.org
________________________________________________________________________

       Furthermore, I think Oracle has to honor the JSPA agreement.
     http://s.apache.org/JCPIsDead       http://s.apache.org/tck-trap

Simone Tripodi | 8 Jun 23:26 2011
Picon

Re: [C3] Release process clarification needed

thanks a lot for your kind help Reinhard!!!
sorry for my lack of knowledge of Groovy, but... do I need an
interpreter to install to execute it?
Many thanks in advance!!!
Simo

http://people.apache.org/~simonetripodi/
http://www.99soft.org/

On Wed, Jun 8, 2011 at 11:19 PM, Reinhard Pötz <reinhard <at> apache.org> wrote:
> On 06/08/2011 09:16 PM, Simone Tripodi wrote:
>>
>> Hi Reinhard/all,
>> can someone explain me please what the third point in the
>> RELEASE_HOWTO.txt means:
>>
>> * set all versions in the generated pom.xml files of all archetypes
>>
>> I didn't see where poms have been generated... thanks in advance!!!
>
> I've just updated the RELEASE_HOWTO.txt.
>
> HTH
>
> I also fixed the sample and the block archetype.
>
> To make things clearer for cocoon-archetype-sample: the sample-archetype
> uses a Groovy script to generate the assembly descriptor on the fly based on
> the content of cocoon-sample and copies all relevant resources to
> src/main/resources/archetype-resources
>
> Maybe there are better ways to achieve this goal with 'standard' Maven
> plugins in the meantime ...
>
> --
> Reinhard Pötz         Founder & Managing Director, Indoqa and Deepsearch
>                        http://www.indoqa.com/people/reinhard-poetz.html
>
> Member of the Apache Software Foundation
> Apache Cocoon Committer, PMC member                  reinhard <at> apache.org
> ________________________________________________________________________
>
>      Furthermore, I think Oracle has to honor the JSPA agreement.
>    http://s.apache.org/JCPIsDead       http://s.apache.org/tck-trap
>

Reinhard Pötz | 9 Jun 07:43 2011
Picon

Re: [C3] Release process clarification needed

On 06/08/2011 11:26 PM, Simone Tripodi wrote:
> thanks a lot for your kind help Reinhard!!!
> sorry for my lack of knowledge of Groovy, but... do I need an
> interpreter to install to execute it?
> Many thanks in advance!!!

No, that's done by the GMaven plugin automatically for you. See the 
pom.xml of the cocoon-archetype-sample module.

--

-- 
Reinhard Pötz         Founder & Managing Director, Indoqa and Deepsearch
                         http://www.indoqa.com/people/reinhard-poetz.html

Member of the Apache Software Foundation
Apache Cocoon Committer, PMC member                  reinhard <at> apache.org
________________________________________________________________________

       Furthermore, I think Oracle has to honor the JSPA agreement.
     http://s.apache.org/JCPIsDead       http://s.apache.org/tck-trap

Simone Tripodi | 9 Jun 12:56 2011
Picon

Re: [C3] Release process clarification needed

thanks a lot Reinhard,
I'm an idiot and started downloading Groovy, installing... :)
I'll let you know my progresses, thanks for your help!
Simo

http://people.apache.org/~simonetripodi/
http://www.99soft.org/

On Thu, Jun 9, 2011 at 7:43 AM, Reinhard Pötz <reinhard <at> apache.org> wrote:
> On 06/08/2011 11:26 PM, Simone Tripodi wrote:
>>
>> thanks a lot for your kind help Reinhard!!!
>> sorry for my lack of knowledge of Groovy, but... do I need an
>> interpreter to install to execute it?
>> Many thanks in advance!!!
>
> No, that's done by the GMaven plugin automatically for you. See the pom.xml
> of the cocoon-archetype-sample module.
>
> --
> Reinhard Pötz         Founder & Managing Director, Indoqa and Deepsearch
>                        http://www.indoqa.com/people/reinhard-poetz.html
>
> Member of the Apache Software Foundation
> Apache Cocoon Committer, PMC member                  reinhard <at> apache.org
> ________________________________________________________________________
>
>      Furthermore, I think Oracle has to honor the JSPA agreement.
>    http://s.apache.org/JCPIsDead       http://s.apache.org/tck-trap
>

Huib Verwey | 9 Jun 18:35 2011
Picon

Building Cocoon + using blocks from cocoon-block-modules without SNAPSHOT versions.

Hi,

I'm trying to build Cocoon 2.2 SVN version with an empty Maven repository on my machine. It does not build, there are some daisy dependencies that cannot be downloaded from anywhere and there are wrong version numbers for Cocoon's own subprojects.

Can somebody fix this situation? It is not only very inconvenient but also a rather embarrassing, newcomers to Cocoon will quickly give up, which is a shame.

Also, I'd like to be able to use some blocks which are still classified as -SNAPSHOT even though they are perfectly useable. Preferably I would like all the blocks from the blocks folder (that are reasonably stable) to be downloadable from an external repository. Because the modules do not have a non-SNAPSHOT version they are not in any repo afaik and I am forced to build cocoon from the source, which gives me the above mentioned troubles.

I appreciate that all the developers have left for Cocoon 3, but please, this is really bad advertising for Cocoon, so please please fix it. As long as there is no shiny Cocoon 3, most people will use Cocoon 2.2 and some people will try to build it from source, if only for the extra modules.

Thanks,

Huib.
 
--
Drs. Huib Verweij
Senior software developer - The Language Archive
Max Planck Institute for Psycholinguistics
P.O. Box 310
6500 AH Nijmegen
The Netherlands

Simone Tripodi | 9 Jun 19:06 2011
Picon

[VOTE] Release Apache Cocoon 3.0.0-alpha-3

Hi all guys,
I'm here to propose the release of Apache Cocoon 3.0.0-alpha-3.

Tags can be found on

https://svn.apache.org/repos/asf/cocoon/cocoon3/tags/cocoon-all/cocoon-all-3.0.0-alpha-3/
https://svn.apache.org/repos/asf/cocoon/cocoon3/tags/cocoon-archetype-block/cocoon-archetype-block-3.0.0-alpha-3/
https://svn.apache.org/repos/asf/cocoon/cocoon3/tags/cocoon-archetype-parent/cocoon-archetype-parent-3.0.0-alpha-3/
https://svn.apache.org/repos/asf/cocoon/cocoon3/tags/cocoon-archetype-sample/cocoon-archetype-sample-3.0.0-alpha-3/
https://svn.apache.org/repos/asf/cocoon/cocoon3/tags/cocoon-archetype-webapp/cocoon-archetype-webapp-3.0.0-alpha-3/
https://svn.apache.org/repos/asf/cocoon/cocoon3/tags/cocoon-controller/cocoon-controller-3.0.0-alpha-3/
https://svn.apache.org/repos/asf/cocoon/cocoon3/tags/cocoon-docs/cocoon-docs-3.0.0-alpha-3/
https://svn.apache.org/repos/asf/cocoon/cocoon3/tags/cocoon-monitoring/cocoon-monitoring-3.0.0-alpha-3/
https://svn.apache.org/repos/asf/cocoon/cocoon3/tags/cocoon-optional/cocoon-optional-3.0.0-alpha-3/
https://svn.apache.org/repos/asf/cocoon/cocoon3/tags/cocoon-parent/cocoon-parent-3.0.0-alpha-3/
https://svn.apache.org/repos/asf/cocoon/cocoon3/tags/cocoon-pipeline/cocoon-pipeline-3.0.0-alpha-3/
https://svn.apache.org/repos/asf/cocoon/cocoon3/tags/cocoon-rest/cocoon-rest-3.0.0-alpha-3/
https://svn.apache.org/repos/asf/cocoon/cocoon3/tags/cocoon-sample/cocoon-sample-3.0.0-alpha-3/
https://svn.apache.org/repos/asf/cocoon/cocoon3/tags/cocoon-sax/cocoon-sax-3.0.0-alpha-3/
https://svn.apache.org/repos/asf/cocoon/cocoon3/tags/cocoon-stax/cocoon-stax-3.0.0-alpha-3/
https://svn.apache.org/repos/asf/cocoon/cocoon3/tags/cocoon-profiling/cocoon-profiling-3.0.0-alpha-3/
https://svn.apache.org/repos/asf/cocoon/cocoon3/tags/cocoon-profiling-firebug/cocoon-profiling-firebug-3.0.0-alpha-3/
https://svn.apache.org/repos/asf/cocoon/cocoon3/tags/cocoon-optional/cocoon-optional-3.0.0-alpha-3/
https://svn.apache.org/repos/asf/cocoon/cocoon3/tags/cocoon-servlet/cocoon-servlet-3.0.0-alpha-3/
https://svn.apache.org/repos/asf/cocoon/cocoon3/tags/cocoon-sitemap/cocoon-sitemap-3.0.0-alpha-3/
https://svn.apache.org/repos/asf/cocoon/cocoon3/tags/cocoon-stringtemplate/cocoon-stringtemplate-3.0.0-alpha-3/
https://svn.apache.org/repos/asf/cocoon/cocoon3/tags/cocoon-wicket/cocoon-wicket-3.0.0-alpha-3/

Maven artifacts can be found on people.apache.org:

/www/people.apache.org/builds/cocoon/org/apache/cocoon/archetype-webapp/cocoon-archetype-webapp/3.0.0-alpha-3
/www/people.apache.org/builds/cocoon/org/apache/cocoon/servlet/cocoon-servlet/3.0.0-alpha-3
/www/people.apache.org/builds/cocoon/org/apache/cocoon/wicket/cocoon-wicket/3.0.0-alpha-3
/www/people.apache.org/builds/cocoon/org/apache/cocoon/root/cocoon-root/3.0.0-alpha-3
/www/people.apache.org/builds/cocoon/org/apache/cocoon/stax/cocoon-stax/3.0.0-alpha-3
/www/people.apache.org/builds/cocoon/org/apache/cocoon/sax/cocoon-sax/3.0.0-alpha-3
/www/people.apache.org/builds/cocoon/org/apache/cocoon/optional/cocoon-optional/3.0.0-alpha-3
/www/people.apache.org/builds/cocoon/org/apache/cocoon/all/cocoon-all/3.0.0-alpha-3
/www/people.apache.org/builds/cocoon/org/apache/cocoon/profiling/cocoon-profiling/3.0.0-alpha-3
/www/people.apache.org/builds/cocoon/org/apache/cocoon/stringtemplate/cocoon-stringtemplate/3.0.0-alpha-3
/www/people.apache.org/builds/cocoon/org/apache/cocoon/archetype-block/cocoon-archetype-block/3.0.0-alpha-3
/www/people.apache.org/builds/cocoon/org/apache/cocoon/parent/cocoon-parent/3.0.0-alpha-3
/www/people.apache.org/builds/cocoon/org/apache/cocoon/sitemap/cocoon-sitemap/3.0.0-alpha-3
/www/people.apache.org/builds/cocoon/org/apache/cocoon/pipeline/cocoon-pipeline/3.0.0-alpha-3
/www/people.apache.org/builds/cocoon/org/apache/cocoon/sample/cocoon-sample/3.0.0-alpha-3
/www/people.apache.org/builds/cocoon/org/apache/cocoon/monitoring/cocoon-monitoring/3.0.0-alpha-3
/www/people.apache.org/builds/cocoon/org/apache/cocoon/archetype-parent/cocoon-archetype-parent/3.0.0-alpha-3
/www/people.apache.org/builds/cocoon/org/apache/cocoon/rest/cocoon-rest/3.0.0-alpha-3
/www/people.apache.org/builds/cocoon/org/apache/cocoon/archetype-sample/cocoon-archetype-sample/3.0.0-alpha-3
/www/people.apache.org/builds/cocoon/org/apache/cocoon/controller/cocoon-controller/3.0.0-alpha-3

Vote will be open for next 72 hours and will be closed on June 12th at
5:00pm CET.
So please cast your votes

[ ] +1, let's release Apache Cocoon 3.0.0-alpha-3
[ ] +/- 0
[ ] -1, because (explain the reason why)

Many thanks in advance, all the best!!!
Simo

http://people.apache.org/~simonetripodi/
http://www.99soft.org/


Gmane