Return-Path: Delivered-To: apmail-cocoon-dev-archive@www.apache.org Received: (qmail 55321 invoked from network); 24 Dec 2003 11:08:51 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 24 Dec 2003 11:08:51 -0000 Received: (qmail 12257 invoked by uid 500); 24 Dec 2003 11:08:21 -0000 Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org Received: (qmail 12038 invoked by uid 500); 24 Dec 2003 11:08:19 -0000 Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: dev@cocoon.apache.org Delivered-To: mailing list dev@cocoon.apache.org Received: (qmail 12023 invoked from network); 24 Dec 2003 11:08:18 -0000 Received: from unknown (HELO out2.smtp.messagingengine.com) (66.111.4.26) by daedalus.apache.org with SMTP; 24 Dec 2003 11:08:18 -0000 X-Sasl-enc: M8RdPoAy1BMK8Xw0Z+/TBw 1072264111 Received: from upaya.co.uk (unknown [213.48.13.39]) by www.fastmail.fm (Postfix) with ESMTP id 1F57748B5C8 for ; Wed, 24 Dec 2003 06:08:29 -0500 (EST) Message-ID: <3FE97360.5090902@upaya.co.uk> Date: Wed, 24 Dec 2003 11:07:12 +0000 From: Upayavira User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624 X-Accept-Language: en-us, en MIME-Version: 1.0 To: dev@cocoon.apache.org Subject: Re: [HEADSUP] Cocoon Ant Task References: <3FE6D90C.1060303@upaya.co.uk> <1072140809.3215.194.camel@ighp> <3FE811FF.2000005@upaya.co.uk> <005101c3c9df$1da9e7b0$1f01a8c0@inferno1> <3FE96021.5080705@upaya.co.uk> <003b01c3ca0b$e00e9950$1f01a8c0@inferno1> In-Reply-To: <003b01c3ca0b$e00e9950$1f01a8c0@inferno1> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Laurent Mauron wrote: >Thanks for the detailed explanations. I checked the Ant documentation and I >am very impressed. I thought Ant was just a 'make'-like tool. > > I plan to deploy an offline version of Cocoon in a first phase and a >CocoonTask as you describe might be exactly what I need to for the >integration part. > > Me too. I'm about to use it on a site. Have Apache serve the static stuff, and Tomcat serve the dynamic stuff, and the Ant task run every night as a cron job to refresh the static content. >I am quite excited about this new component to say the least. > > Me too. I'm surprised about how much it seems to change the feel of Cocoon's offline functionality. Regards, Upayavira > > > >----- Original Message ----- >From: "Upayavira" >To: >Sent: Wednesday, December 24, 2003 10:45 AM >Subject: Re: [HEADSUP] Cocoon Ant Task > > > > >>Laurent Mauron wrote: >> >> >> >>>Upayavira, >>> >>>That sounds very interesting. I am not familiar with Ant and other >>> >>> >standard > > >>>java tools. What's the advantage of wrapping the cocoon cli with an ant >>>task? >>> >>> >>> >>> >>You aren't actually 'wrapping', you're 'replacing'. The Ant task does >>much the same as the CLI - it interfaces with Cocoon via the CocoonBean. >> >>The benefits of using Ant are the array of Ant tasks that are available >>to you - tasks to copy files, unpack archives, send files by FTP, SCP, >>doing XSLT transformations, checking into/out of CVS, etc, etc. Around >>the functionality of Cocoon you can build a more powerful deployment >>system using the lego blocks that Ant provides. >> >>In many ways, I see the Ant task overtaking the CLI as the recommended >>way to access Cocoon's offline functionality, because of this >>flexibility within Ant. >> >>Also, because Cocoon is running within the same JVM as Ant, there is a >>minimal impact in terms of using Ant - Ant itself being relatively >>lightweight (the JVM startup being the slow part). So, to my mind, you >>get many benefits with few drawbacks. >> >>To really make the CocoonTask integrate with Ant, and make it really >>useful, I suspect it will need a few enhancements. For example, the >>xconf language it uses (and shares with the cli.xconf) doesn't really >>offer much support for the list of URIs to generate to have been created >>by a previous Ant task. So, when people start actively using the >>CocoonTask, I suspect it will want some improvement. But lets see the >>use cases emerge before we do anything. >> >>I have already written some basic docs for the CocoonTask. I've just got >>to make sure they're valid xdocs before I can commit them - hopefully >>within a week or so. >> >>I hope this answers your question. >> >>Regards, Upayavira >> >> >> >>>Laurent >>> >>>----- Original Message ----- >>>From: "Upayavira" >>>To: >>>Sent: Tuesday, December 23, 2003 10:59 AM >>>Subject: Re: [HEADSUP] Cocoon Ant Task >>> >>> >>> >>> >>> >>> >>>>David Crossley wrote: >>>> >>>> >>>> >>>> >>>> >>>>>Upayavira wrote: >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>>>Having now seen it work well, I will document it properly soon. I will >>>>>>also add it to the list of external tasks that is maintained by the >>>>>> >>>>>> >Ant > > >>>>>>project (unless anyone objects). >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>Please do. >>>>> >>>>>I have not seen much discussion here on cocoon-dev about testing it. >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>After your troubles, I had a private discussion with Sylvain, who tested >>>>it and it worked. I've also now tested a separate checkout on both >>>>Windows and Linux, which worked fine (except for a requiring an NPE >>>>patch that was nothing to do with the Ant task). >>>> >>>> >>>> >>>> >>>> >>>>>Anyway, Upayavira, remember the trouble that i had on the forrest-dev >>>>>thread: http://marc.theaimsgroup.com/?t=106604813100001 >>>>>Well it works for me now with yesterday's Cocoon cvs and following >>>>>the instructions in that thread. >>>>> >>>>> >>>>> >>>>> >>>>> >>>>Ahhh. Great. Thanks for that. I'm pleased. >>>> >>>> >>>> >>>> >>>> >>>>>Dunno what changed, but it works. >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>Dunno either. The error you got was one that I got a lot in development, >>>>but haven't had at all since I committed the code. >>>> >>>>I've got docs half written. I'll commit them soon. >>>> >>>>Regards, Upayavira >>>> >>>> >>>> >>>> >>>> >>>> >>> >>> >>> >>> >> >> > > > >