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. I am quite excited about this new component to say the least. ----- Original Message ----- From: "Upayavira" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> 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" <[EMAIL PROTECTED]> > >To: <[EMAIL PROTECTED]> > >Sent: Tuesday, December 23, 2003 10:59 AM > >Subject: Re: [HEADSUP] Cocoon Ant Task > > > > > > > > > >>David Crossley wrote: > >> > >> > >> > >>>Upayavira wrote: > >>><snip/> > >>> > >>> > >>> > >>> > >>>>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 > >> > >> > >> > >> > > > > > > > > > >
