You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by dandart <da...@googlemail.com> on 2012/04/18 18:51:11 UTC
Maven 2 to 3 migration problem
Hi, I'm moving our project from maven2 to maven3.
However I'm getting the following errors:
https://gist.github.com/2414962
My pom.xml looks like this:
https://gist.github.com/2414936
& this confuses me.
I was told to put versions into it everywhere but it still didn't help.
Does anyone know a solution?
Cheers
Dan
--
View this message in context: http://maven.40175.n5.nabble.com/Maven-2-to-3-migration-problem-tp5649678p5649678.html
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: Maven 2 to 3 migration problem
Posted by Matt Walsh <mw...@chartwelltechnology.com>.
I can help get rid of the warnings.
You have the maven-antrun-plugin declared 4 times. I think what you want
is 4 executions within 1 declaration.
You have the maven-releases-plugin declared 2 times in your
pluginManagement.
As far as the error is concerned, your build doesn't seem to like the
dependencyManagement.status field in the commons-httpclient pom for some
reason. We use version 3.1 of that dependency with maven 3 no problem. I
don't suppose the above issues are causing some kind of Maven parsing
issue? Perhaps someone with more knowledge than I will jump in on that
one.
Matt
> -----Original Message-----
> From: dandart [mailto:dandart@googlemail.com]
> Sent: Wednesday, April 18, 2012 10:51 AM
> To: users@maven.apache.org
> Subject: Maven 2 to 3 migration problem
>
> Hi, I'm moving our project from maven2 to maven3.
> However I'm getting the following errors:
>
> https://gist.github.com/2414962
>
> My pom.xml looks like this:
>
> https://gist.github.com/2414936
>
> & this confuses me.
> I was told to put versions into it everywhere but it still didn't
help.
>
> Does anyone know a solution?
>
> Cheers
> Dan
>
> --
> View this message in context:
http://maven.40175.n5.nabble.com/Maven-2-
> to-3-migration-problem-tp5649678p5649678.html
> Sent from the Maven - Users mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
______________________________________________________________________
This message, including any attachments, is confidential and contains information intended only for the person(s) named above. Any other distribution, copying or disclosure is strictly prohibited. If you are not the intended recipient or have received this message in error, please notify us immediately by reply email and permanently delete the original transmission from all of your systems and hard drives, including any attachments, without making a copy.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Maven 2 to 3 migration problem
Posted by dandart <da...@googlemail.com>.
I'm more concerned with the parts below the snip - it appears there are two
problems.
--
View this message in context: http://maven.40175.n5.nabble.com/Maven-2-to-3-migration-problem-tp5649678p5649780.html
Sent from the Maven - Users mailing list archive at Nabble.com.
Re: Maven 2 to 3 migration problem
Posted by "martin.eisengardt" <ma...@googlemail.com>.
I see. You are using the java dependencies for build plugins? Otherwise
this won't make any sense.
Dependencies for build plugins should be defined alongside the build plugin
itself and not at the regular dependencies. The top level dependencies tag
is used for the project dependencies. See
http://maven.apache.org/pom.html#Plugins for details. Although I will try
to fix php-maven you should change this in your pom file and retry.
Some other remarks:
jar dependencies are working with php-maven 2.0 but you may change them to
phar dependencies of the php-maven repository. For example:
http://nexus.php-maven.org/index.html#nexus-search;gav~de.phpunit~PHPUnit~~~~kw,versionexpand(synchronized
fdaily with official phpunit pear channel)
http://nexus.php-maven.org/index.html#nexus-search;gav~com.zend.framework~framework~~~~kw,versionexpand(synchronized
daily with zend homepage)
On Thu, Apr 19, 2012 at 10:21 AM, dandart <da...@googlemail.com> wrote:
> > Is one of your dependencies a java project?
> Yes - we use:
> net.java.dev.jets3t/jets3t
> net.java.dev.jets3t/synchronize
>
> > 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.
>
> Hi,
> Here is the affected portion with -X:
>
> https://gist.github.com/2419599
>
> Cheers
> Dan
>
> --
> View this message in context:
> http://maven.40175.n5.nabble.com/Maven-2-to-3-migration-problem-tp5649678p5651187.html
> Sent from the Maven - Users mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
Re: Maven 2 to 3 migration problem
Posted by dandart <da...@googlemail.com>.
> Is one of your dependencies a java project?
Yes - we use:
net.java.dev.jets3t/jets3t
net.java.dev.jets3t/synchronize
> 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.
Hi,
Here is the affected portion with -X:
https://gist.github.com/2419599
Cheers
Dan
--
View this message in context: http://maven.40175.n5.nabble.com/Maven-2-to-3-migration-problem-tp5649678p5651187.html
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Maven 2 to 3 migration problem
Posted by "martin.eisengardt" <ma...@googlemail.com>.
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 <wa...@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-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
Re: Maven 2 to 3 migration problem
Posted by Wayne Fay <wa...@gmail.com>.
> However I'm getting the following errors:
>
> https://gist.github.com/2414962
...
> Does anyone know a solution?
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-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org