We are all mortals...:-) However, it looks like it has been fixed in 3.0-alpha-1. Mike, try 3.0-alpha-5! When you've tried it, there is no going back...:-) http://www.sonatype.com/people/2009/11/maven-30-new-and-improved-formula/
/Anders On Tue, Dec 8, 2009 at 06:55, Wayne Fay <wayne...@gmail.com> wrote: > > Child project 2 has the exact same setup "however" it changes the > dependency > > defined in the plugin to be dependent on a different project. > > > > configurations. It always seems that the first time a plugin is loaded > that > > is the classpath used for that plugin whenever it is executed. > > This is a (very well) known bug in Maven 2. The "first" declaration of > a plugin's dependencies "wins" (as plugin containers are initialized > once per build) so you need to include all dependencies for all uses > of a given plugin in the "first" declaration. See JIRA: > http://jira.codehaus.org/browse/MNG-1949 > > I'm actually surprised Anders didn't know this one... ;-) > > Wayne > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
