Return-Path: Delivered-To: apmail-cocoon-users-archive@www.apache.org Received: (qmail 15189 invoked from network); 10 Sep 2009 15:42:35 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 10 Sep 2009 15:42:35 -0000 Received: (qmail 8093 invoked by uid 500); 10 Sep 2009 15:42:34 -0000 Delivered-To: apmail-cocoon-users-archive@cocoon.apache.org Received: (qmail 8021 invoked by uid 500); 10 Sep 2009 15:42:34 -0000 Mailing-List: contact users-help@cocoon.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: users@cocoon.apache.org List-Id: Delivered-To: mailing list users@cocoon.apache.org Received: (qmail 8013 invoked by uid 99); 10 Sep 2009 15:42:34 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 10 Sep 2009 15:42:34 +0000 X-ASF-Spam-Status: No, hits=2.8 required=10.0 tests=HTML_FONT_FACE_BAD,HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [194.54.146.71] (HELO everett-ict.com) (194.54.146.71) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 10 Sep 2009 15:42:21 +0000 Received: from ([10.100.1.8]) by mex1.everett-ict.com with ESMTP id GGGPFJ1.45762; Thu, 10 Sep 2009 17:42:00 +0200 Received: from strega.tech.everett.it ([81.174.56.204]) by roadland.blue.webflex.net (Sun Java System Messaging Server 6.2-4.03 (built Sep 22 2005)) with ESMTPSA id <0KPR00MIAI9ZXT20@roadland.blue.webflex.net> for users@cocoon.apache.org; Thu, 10 Sep 2009 17:42:00 +0200 (CEST) Date: Thu, 10 Sep 2009 17:41:59 +0200 From: =?ISO-8859-1?Q?Francesco_Chicchiricc=F2?= Subject: Re: Starting out with Cocoon 2.2 In-reply-to: <4AA91358.7060308@onehippo.com> To: users@cocoon.apache.org Message-id: <32F9C204-E88B-4F16-B413-4424309A8603@everett.it> MIME-version: 1.0 X-Mailer: Apple Mail (2.936) Content-type: multipart/alternative; boundary="Boundary_(ID_zHSGKyHdqBqNjOBfLNe9lw)" References: <4AA8DA7F.8060804@publishingtechnology.com> <4AA8E984.8040301@searchevent.co.uk> <4AA90192.5050502@oulu.fi> <4AA91358.7060308@onehippo.com> X-Virus-Checked: Checked by ClamAV on apache.org --Boundary_(ID_zHSGKyHdqBqNjOBfLNe9lw) Content-type: text/plain; charset=UTF-8; format=flowed; delsp=yes Content-transfer-encoding: quoted-printable On 10/sep/09, at 16:55, Jeroen Reijn wrote > Well I think that some people have put Cocoon on a low profile. =20 > There were a lot of great frameworks added to the ASF code base =20 > lately, which made people broaden their perspective. > > I don't really think that people quit working with/on Cocoon, =20 > because Cocoon 2.1 is stable and a lot of people are using it. =20 > Cocoon 2.2 however has slowed down in development, but did not =20 > really stop. Some developers have started working on Cocooon 3.0 =20 > alpha, which is still under development. > > One of the great things of a community is that the more people get =20 > involved into the project, the more the project evolves. Don't be =20 > shy to still keep working with Cocoon. One of the things on my todo =20= > list is to do some work on the Cocoon JCR block. I don't really have =20= > an estimate on when I can find some time, but I hope it to be soon. ...which in turn would result in Hippo 7 to get a Cocoon front-end, =20 right? :-) > Andre Juffer wrote: >> Francesco Chicchiricc=C3=B2 wrote: >>> On 10/sep/09, at 15:05, Ellis Pritchard wrote: >>> >>>> Lamentable indeed. >>>> >>>> Having taken a break from Cocoon 2.1 at work, and returned to =20 >>>> 2.2, after much pain and frustration at recreating what was in =20 >>>> cocoon using 'pure' java and spring mvc + freemarker (urgh) + =20 >>>> 1000's of lines of horrible java to do stuff cocoon did for free, =20= >>>> I realize how much I miss the simple power of the platform. For =20 >>>> XML content, there is simply nothing better. >>>> >>>> 2.2 really should have been finished: user docs, the halfway =20 >>>> house between spring and Avalon, missing blocks (eventcache =20 >>>> anyone?)... it's all so close and yet so far. >>>> >>>> I'd love to get involved in polishing this stuff, but I've never =20= >>>> really been part of the 'community', just finding and reporting =20 >>>> tricky defects! >>>> >>>> Is there any interest out there for futher work on 2.2? >>> >>> I am. >> I am as well. It would be a shame if cocoon would not be developed =20= >> further. It is really a great platform! >>> >>>> On 10 Sep 2009, at 12:56, David Legg =20 >>>> >>> > wrote: >>>> >>>>> Hi David, >>>>> >>>>>> I'm just about to embark on a new project... I'd like to use =20 >>>>>> Cocoon 2.2 for this, but I'm concerned about the apparent lack =20= >>>>>> of support for it. >>>>> >>>>> It is true that Cocoon has hit a low point at the moment and I'm =20= >>>>> sure many of us wonder if it will ever recover. Many of the =20 >>>>> original contributors have moved on to other things and =20 >>>>> officially version 2 (and 2.2) are in 'maintenance mode'. =20 >>>>> Version 3 is still being worked on but to be honest it looks so =20= >>>>> different that you will be starting again from scratch compared =20= >>>>> to version 2. >>>>> >>>>> It's a great shame as I really thought version 2.2 was beginning =20= >>>>> to gain traction. >>>>> >>>>>> Can anyone suggest any resources that will help me get started =20= >>>>>> with Cocoon 2.2? >>>>> >>>>> I would archive that book on version 2! It will be of little =20 >>>>> use to you when working with 2.2. >>>>> >>>>> Most of the useful documentation can be found here: - >>>>> >>>>> http://cocoon.zones.apache.org/dev-docs/2.2/1159_1_1.html >>>>> >>>>> But you should be aware that this is the 'published' version of =20= >>>>> the documentation. It may be the case that the 'unpublished' =20 >>>>> versions are more up to date. To get to them you can click on =20 >>>>> the link at the bottom of the page where it mentions 'Errors and =20= >>>>> Improvements'. This link will take you to the Daisy CMS which =20 >>>>> is what Cocoon members use to write and edit documentation =20 >>>>> before it gets published. >>>>> >>>>> Yes!... It is a horrible mess and I have commented about this =20 >>>>> before but was persuaded it was for the best. >>>>> >>>>>> I'm concerned that interest in and support for Cocoon is dying =20= >>>>>> out. Would I be better off choosing a completely different =20 >>>>>> technology for my project? >>>>> >>>>> I would say think seriously before you commit another year or =20 >>>>> two of your life to learning it! >>>>> >>>>> Regards, >>>>> David Legg --=20 Francesco Chicchiricc=C3=B2 Delivery Manager everett Italia =E2=96=B8 TRUSTED TO KNOW Head Office Via Torino, 2 - 20123 Milano - Italia Tel: +39 02 72546847 Fax: +39 02 72546418 Technology Centre Via Federico Fellini, 2 G2/1 - 65010 Spoltore (PE) - Italia Tel: +39 085 2120342 / +39 085 2120537 Fax: +39 085 2120342 / +39 085 2120537 Mob: +39 329 0573276 e-mail: francesco.chicchiricco@everett.it Web: http://www.everett.it --Boundary_(ID_zHSGKyHdqBqNjOBfLNe9lw) Content-type: text/html; charset=UTF-8 Content-transfer-encoding: quoted-printable
On 10/sep/09, at = 16:55, Jeroen Reijn wrote

Well = I think that some people have put Cocoon on a low profile. There were a = lot of great frameworks added to the ASF code base lately, which made = people broaden their perspective.

I don't really think that = people quit working with/on Cocoon, because Cocoon 2.1 is stable and a = lot of people are using it. Cocoon 2.2 however has slowed down in = development, but did not really stop. Some developers have started = working on Cocooon 3.0 alpha, which is still under = development.

One of the great things of a community is that the = more people get involved into the project, the more the project evolves. = Don't be shy to still keep working with Cocoon. One of the things on my = todo list is to do some work on the Cocoon JCR block. I don't really = have an estimate on when I can find some time, but I hope it to be = soon.

...which in turn would = result in Hippo 7 to get a Cocoon front-end, right? = :-)

Andre Juffer = wrote:
Francesco Chicchiricc=C3=B2 = wrote:
On 10/sep/09, at 15:05, Ellis Pritchard = wrote:

Lamentable = indeed.

Having = taken a break from Cocoon 2.1 at work, and returned to 2.2, after much = pain and frustration at recreating what was in cocoon using 'pure' java = and spring mvc + freemarker (urgh) + 1000's of lines of horrible java to = do stuff cocoon did for free, I realize how much I miss the simple power = of the platform. For XML content, there is simply nothing = better.

2.2 = really should have been finished: user docs, the halfway house between = spring and Avalon, missing blocks (eventcache anyone?)... it's all so = close and yet so = far.

I'd = love to get involved in polishing this stuff, but I've never really been = part of the 'community', just finding and reporting tricky = defects!

Is = there any interest out there for futher work on = 2.2?

I = am.
I am as well. = It would be a shame if cocoon would not be developed further. It is = really a great platform!

On 10 = Sep 2009, at 12:56, David Legg <david.legg@searchevent.co.uk<= /a> <mailto:david.legg@searchevent= .co.uk>> = wrote:

Hi = David,

I'm = just about to embark on a new project... I'd like to use Cocoon 2.2 for = this, but I'm concerned about the apparent lack of support for = it.

It is true that Cocoon has hit a = low point at the moment and I'm sure many of us wonder if it will ever = recover.  Many of the original contributors have moved on to other = things and officially version 2 (and 2.2) are in 'maintenance mode'. =  Version 3 is still being worked on but to be honest it looks so = different that you will be starting again from scratch compared to = version = 2.

It's a great shame as I really = thought version 2.2 was beginning to gain = traction.

Can = anyone suggest any resources that will help me get started with Cocoon = 2.2?
<= blockquote type=3D"cite">

I would archive that book on = version 2!  It will be of little use to you when working with = 2.2.

Most of the useful documentation = can be found here: = -

http://= cocoon.zones.apache.org/dev-docs/2.2/1159_1_1.html

But you should be aware that = this is the 'published' version of the documentation.  It may be = the case that the 'unpublished' versions are more up to date.  To = get to them you can click on the link at the bottom of the page where it = mentions 'Errors and Improvements'.  This link will take you to the = Daisy CMS which is what Cocoon members use to write and edit = documentation before it gets = published.

Yes!... It is a horrible mess = and I have commented about this before but was persuaded it was for the = best.

I'm = concerned that interest in and support for Cocoon is dying out. Would I = be better off choosing a completely different technology for my = project?

I would say think seriously = before you commit another year or two of your life to learning = it!

Regards,
David = Legg

-- 

Francesco = Chicchiricc=C3=B2
Delivery Manager

tt = Italia 

Head = Office
Via Torino, 2 - 20123 Milano - Italia
Tel:
+39 02 = 72546847
Technology Centre
Via = Federico Fellini, 2 G2/1 - 65010 Spoltore (PE) - Italia
Tel:
+39 085 2120342 / = +39 085 2120537
Mob:
+39 329 = 0573276
Web:

=
=

= --Boundary_(ID_zHSGKyHdqBqNjOBfLNe9lw)--