As far as I can see the maven goal creates a new ear that is cactified. 
The Ant task on the other hand cactifies an existing ear. Both way should be
supported eventually but maybe its a good idea to have the maven goal and the 
ant task seperated for this release.

So, how do we want it? Should I commit my changes to cactifyear or should we 
release a 1.7.1 first that is free from cargo dependencies?

/Magnus

> -----Original Message-----
> From: Vincent Massol [mailto:[EMAIL PROTECTED]
> Sent: Monday, April 25, 2005 3:42 PM
> To: 'Cactus Developers List'
> Subject: RE: Cactus 1.7.1
> 
> 
> It's in jakarta-cactus/integration/maven/plugin.jelly (search 
> for "<goal
> name="cactus:cactifyear"").
> 
> Let us know if you need help in understanding it.
> 
> Thanks
> -Vincent
> 
> > -----Original Message-----
> > From: Magnus Grimsell [mailto:[EMAIL PROTECTED]
> > Sent: lundi 25 avril 2005 15:33
> > To: Cactus Developers List
> > Subject: RE: Cactus 1.7.1
> > 
> > Where is the source code or documentation for the cactifyear goal?
> > I'm rather new to maven so it's a little bit confusing.
> > 
> > /Magnus
> > 
> > > -----Original Message-----
> > > From: Felipe Leme [mailto:[EMAIL PROTECTED]
> > > Sent: Monday, April 25, 2005 3:03 PM
> > > To: Cactus Developers List
> > > Subject: RE: Cactus 1.7.1
> > >
> > >
> > > Hi again,
> > >
> > > On Mon, 25 Apr 2005 14:46:49 +0200, "Vincent Massol"
> > > <[EMAIL PROTECTED]> wrote:
> > >
> > > > is in CVS HEAD at any time. Thus I would prefer not to do
> > > branches. I've had
> > >
> > > I agree with you, branches are hard to maintain. What I meant
> > > (and I think I was not clear) is that the 1.7.1 would be more
> > > of a checkpoint/tag than a branch. In other words, all new
> > > fixes to 1.7.1 would go to 1.8.0, not 1.7.2.
> > >
> > > > Otherwise we simply deliver the new <cactifyear> Ant task
> > > and the Maven
> > > > plugin remains unchanged.
> > >
> > > Ok, now I get it. The Ant integration didn't support
> > > cactifyear and Maven implemented it from scratch. Makes sense
> > > them - I was afraid people would get those nasty
> > > NoClassDefFound exceptions (which alone are hard to debug,
> > > imagine wrapped in a Jelly call :-).
> > >
> > > > Felipe, have you had a look at Magnus' patch? I think
> > > you're worrying
> > > > unnecessarily :-)
> > >
> > > Sorry, my bad...
> > >
> > > -- Felipe
> > >
> > >
> > > 
> ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > For additional commands, e-mail: 
> [EMAIL PROTECTED]
> > >
> > >
> > 
> > 
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 
> ___________________________________________________________
> Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français !
> Yahoo! Mail : http://fr.mail.yahoo.com
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to