> 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: [email protected] For additional commands, e-mail: [email protected]
