Yes, this will solve some of the warnings. But maybe there is an issue with
php-maven too. I am wondering why php-maven complains to understand
"apache-httpclient" dependency.

Is one of your dependencies a java project? Maybe this is an issue with
php-maven too that it behaves wrong with some types of dependencies.
Please send me the debug output (cli option -X) directly to let me check
there is nothing wrong with php-maven itself.


On Wed, Apr 18, 2012 at 7:18 PM, Wayne Fay <wayne...@gmail.com> wrote:

>
> You pom looks like:
> <build><plugins>
> <plugin><!-- antrun -->
> <plugin><!-- antrun -->
> <plugin><!-- antrun -->
> and similar situation with m-exec-p.
>
> This is not supported and will make M3 complain. You need to change
> that into a SINGLE declaration of each plugin, and then use multiple
> EXECUTION nodes to specify the various configurations.
>
> While we're talking about it, how should this error message be changed
> to help people understand this better in the future -- it is pretty
> clear to me:
> [WARNING] 'build.plugins.plugin.(groupId:artifactId)' must be unique
> but found duplicate declaration of plugin
> org.apache.maven.plugins:maven-antrun-plugin @ line 217, column 21
>
> Wayne
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>

Reply via email to