jakarta-cactus-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vincent Massol" <vmas...@pivolis.com>
Subject RE: behaviour of the maven plugin
Date Thu, 01 Apr 2004 18:12:06 GMT
Hi Peter,

> -----Original Message-----
> From: Peter Bright [mailto:Peter.Bright@orbian.com]
> Sent: 01 April 2004 18:36
> To: Cactus Users List (E-mail)
> Subject: behaviour of the maven plugin
> 
> Hello,
> 
> Is it really a Good Thing that the maven plugin causes the use of ear-
> plugin
> 1.3 and ejb-plugin 1.2?  maven rc2 ships with newer versions of both
(1.4
> and 1.3, respectively).  Because ear 1.4 has breaking changes, this
seems
> less than ideal to me.  A project.xml that works with 1.4 doesn't work
> with
> 1.3 (and vice versa -- 1.4 needs ear.module which 1.3 doesn't
recognize,
> and
> 1.3 needs ear.bundle which 1.4 does something stupid with).

You're right. I have removed the explicit dependencies on the EAR and
WAR plugins.

> 
> The upshot of this is that if one installs the plugin, maven (upon
> unpacking
> the plugin to the ~/.maven/plugins) grabs these old versions, and
breaks
> the
> project on all subsequent builds.
> 
> This to me seems like quite undesirable behaviour.  I appreciate that
the
> cactus plugin calls one of the ear goals (<attainGoal
name="ear:load"/>)
> and
> so needs that goal available and working, but that doesn't seem to me
to
> be
> a good enough reason to break things.  I appreciate also that it's not
> really the cactus plugin's fault that the ear plugin has changed in
this
> incompatible way.  I accept that omitting this dependency is quite
> contrary
> to maven's generally desirable handling of versioned dependencies.
But I
> feel that nonetheless the change should be made.  Particularly
problematic
> is that the result is that /any/ project gets broken, because of the
> pollution of the plugin directory.

Done in CVS! Thanks!

> 
> I notice that as of
> http://nagoya.apache.org/bugzilla/show_bug.cgi?id=27351
> the cactus plugin now makes use of the new 1.4 property, but it
appears
> (judging by
> http://cvs.apache.org/viewcvs.cgi/*checkout*/jakarta-
> cactus/integration/mave
> n/project.xml?content-type=text%2Fplain) that it still has as a
dependency
> the older ear plugin, so the fix doesn't seem to be a particularly
good
> one
> -- installing a new cactus plugin will still result in plugin
pollution.
> 
> Regards,
> 
> Peter

-Vincent


Mime
View raw message