You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Julie Chi <Ju...@so.mnscu.edu> on 2012/01/31 17:57:24 UTC

Maven 3.0.3 generated different runtime classpath with the same POM

I'm upgrading Maven from 2.2.1 to 3.0.3, it BUILD SUCCESS. However the runtime classpath(xxx.war \WEB-INF\lib)  are generated differently.  Ex. We defined  version 3.2.1.ga for hibernate-annotations, Maven2.2.1 generates version as it's defined 3.2.1.ga.jar.  However Maven 3.0.3  generated version 3.3.1.ga.jar and also a lot of more  jars  like titles-*.jar, spring-ldap-*.jar, ojdbc-14.jar .... Those are not generated by Maven 2.2.1 . I'm using the same POM , means the same version( 2.1.1) for maven-war-plugin.

-Julie


Re: Maven 3.0.3 generated different runtime classpath with the same POM

Posted by Sebastian Otaegui <fe...@gmail.com>.
Can you post your pom?

On Feb 1, 2012 1:15 AM, "Jörg Schaible" <Jo...@scalaris.com> wrote:
>
> Sebastian Otaegui wrote:
>
> > You can try doing 'mvn dependency:tree' to look at the artifact
resolution
> > tree with both versions.
>
> This does not help, since the plugin uses a dependency resolution
algorithm
> similar to M2.
>
> - Jörg
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>

Re: Maven 3.0.3 generated different runtime classpath with the same POM

Posted by Jörg Schaible <Jo...@scalaris.com>.
Sebastian Otaegui wrote:

> You can try doing 'mvn dependency:tree' to look at the artifact resolution
> tree with both versions.

This does not help, since the plugin uses a dependency resolution algorithm 
similar to M2.

- Jörg



---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


Re: Maven 3.0.3 generated different runtime classpath with the same POM

Posted by Sebastian Otaegui <fe...@gmail.com>.
You can try doing 'mvn dependency:tree' to look at the artifact resolution
tree with both versions.


On Tue, Jan 31, 2012 at 10:57 AM, Julie Chi <Ju...@so.mnscu.edu> wrote:

> I'm upgrading Maven from 2.2.1 to 3.0.3, it BUILD SUCCESS. However the
> runtime classpath(xxx.war \WEB-INF\lib)  are generated differently.  Ex. We
> defined  version 3.2.1.ga for hibernate-annotations, Maven2.2.1 generates
> version as it's defined 3.2.1.ga.jar.  However Maven 3.0.3  generated
> version 3.3.1.ga.jar and also a lot of more  jars  like titles-*.jar,
> spring-ldap-*.jar, ojdbc-14.jar .... Those are not generated by Maven 2.2.1
> . I'm using the same POM , means the same version( 2.1.1) for
> maven-war-plugin.
>
> -Julie
>
>


-- 
Those who do not understand Unix are condemned to reinvent it, poorly.
Any sufficiently recent Microsoft OS contains an ad hoc,
informally-specified, bug-ridden, slow implementation of half of Unix.