Reinhard Poetz wrote:
> 
> 
> > -----Original Message-----
> > From: Berin Loritsch [mailto:[EMAIL PROTECTED] 
> > Sent: Tuesday, September 30, 2003 2:31 PM
> > To: [EMAIL PROTECTED]
> > Subject: Re: Ant/Maven/Centipede discussion
> > 
> > 
> > Kevin O'Neill wrote:
> > >>Again, I am not pressing for Maven, but these are the 
> > features that we 
> > >>get for free with it.  Since it looks like we are using 
> > ANT, how do we 
> > >>resolve these needs?
> > > 
> > > 
> > > Umm I'm not sure that this is the case. There is nothing 
> > I've seen or 
> > > used with Maven that can't be done with ant 1.6 (import / 
> subant / 
> > > antlib etc). The bous is that you get to set the 
> > dependencies between 
> > > build targets not mavne (which as can be seen from the 
> > latest set of 
> > > issues with aspectj) can be very difficult to resolve.
> > 
> > 
> > The thing is that Ant 1.6 as promissing as it sounds is not 
> > released yet. If we keep the same build system, thats fine.  
> > However, I would prefer we do this with something we can 
> > expect to find *installed* on a developer's machine.  
> 
> Cocoon comes with its own Ant - there's no need for an 
> installed Ant on
> the developer's machine. So if we decide to use Ant 1.6 the user will
> get it automatically.
> 
> Reinhard
> 

But that only covers sources located inside the cocoon source tree. What about 
developers that want to create their own  blocks? As it is now the only way to do that 
is to put them into the cocoon source tree, edit the Gump descriptor, etc. How would 
you achieve that these third party blocks to be project managed in any acceptable way 
- such as putting them into some CVS module of their own or at least away from the 
cocoon source tree - ? Somehow there needs to be some kind of plugin or ant add-on 
that will also work without having to invoke cocoons specific build script. Or maybe 
you imply to say that any machine you wish to develop a cocoon block on be outfitted 
with an installed cocoon instance just to build the project?

The way I have been able to develop seperate blocks has been to create a custom Maven 
plugin that simulates some of the tasks that are defined in the cocoon block build 
system, such as patching configuration files and sitemaps, copying resources, etc. 
Surely this is something that cocoon lacks atm.

-Unico-

Reply via email to