Hi Henrik, Henrik Niehaus wrote:
> Hi Maven users, > > I'm having problems with two plugins, which both define a custom > packaging type. The packaging types are source-plugin and binary-plugin, > which are defined in a private maven plugin and warpath, which is > defined in the warpath plugin. > > If I run the project with both plugins defined, only the first plugin > seems to be taken into account. E.g. if our private plugin is defined > above the warputh plugin, "source-plugin" and "binary-plugin" can be > resolved and "warpath" cannot be resolved. Same thing vice versa, if the > warputh plugin is defined above out plugin, "warpath" can be resolved, > "source-plugin" and "binary-plugin" not. > > Plugins are defined this way: > > <plugin> > <groupId>com.company</groupId> > <artifactId>maven-rcpbuild-plugin</artifactId> > <version>1.0.3</version> > <extensions>true</extensions> > </plugin> > <plugin> > <groupId>org.appfuse</groupId> > <artifactId>maven-warpath-plugin</artifactId> > <version>2.0.2</version> > <extensions>true</extensions> > <executions> > <execution> > <goals> > <goal>add-classes</goal> > </goals> > </execution> > </executions> > </plugin> > > Running the project with our plugin and without the warpath plugin works > and vice versa. > If I run the same configuration with maven 2.2.1, it works as expected. > Also the plugin order is irrelevant. > > Is this a limitation of maven 2.0.*, or a bug or am I doing something > wrong? I'm lost with this problem. Any hints are appreciated. > > Let me know, if some relevant information is missing. Please look into the POMs of the plugins and tell whether they declare a dependency to another plugin themselves. If yes, which ones? - Jörg --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
