> -----Original Message----- > From: Jason van Zyl [mailto:[EMAIL PROTECTED] > Sent: 26 November 2003 16:22 > To: Maven Developers List > Subject: Re: Adding explicit plugin dependencies > > On Wed, 2003-11-26 at 03:55, Vincent Massol wrote: > > Hi, > > > > I'd like to start adding explicit dependencies for maven plugins. > > +1 > > The plugin dependency mechanism will need a little adjusting but that's > not that big of a deal. I'm not sure how much of the dependency > resolving code Brett merged from rc2-unstable but that code is much > cleaner and could easily be adjusted to glean deps from the POM instead > of doing the namespace voodoo thing.
Question: Is there someone who could help with this voodoo thing? (I'm still not very comfortable with Maven core) [snip] > > What would be a real helper to add these dependencies would be a > > optional "strict" mode for <attainGoal>. By strict, I mean that only > > goals from declared dependencies would be allowed to run. Others will > > fail with a warning stating that it is missing a dependency. This would > > allow to easily identify dependencies. However, I'm not sure how easy > > (or how hard) it would be to implement this optional strict mode. Any > > idea? > > Not sure what you mean entirely here. By "goals from declared > dependencies" you mean goals belonging to plugins that have been > declared in the POM? Yes, that's what I mean. I think I mean the same thing as you said above: "could easily be adjusted to glean deps from the POM instead of doing the namespace voodoo thing". Thanks -Vincent --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
