cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Felix Knecht <fe...@otego.com>
Subject DependencyManagement in root pom
Date Tue, 24 Apr 2007 11:52:09 GMT
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I noticed a strange behaviour:

The version in the root pom dependenyManagement section does overwrite
the version in the block pom when installing the block locally: e.g.
cocoon-batik-impl

In the block pom version 1.0.0-RC1-SNAPSHOT is set
In the root pom dependencyManagement version 1.0.0-SNAPSHOT is set.

Installing the batik-impl block will result in the following:
Building jar:
/home/felix/svn/apache/cocoon/trunk/blocks/cocoon-batik/cocoon-batik-impl/target/cocoon-batik-impl-1.0.0-RC1-SNAPSHOT.jar
[INFO] [install:install]
[INFO] Installing
/home/felix/svn/apache/cocoon/trunk/blocks/cocoon-batik/cocoon-batik-impl/target/cocoon-batik-impl-1.0.0-RC1-SNAPSHOT.jar
to
/home/felix/.m2/repository/org/apache/cocoon/cocoon-batik-impl/1.0.0-SNAPSHOT/cocoon-batik-impl-1.0.0-SNAPSHOT.jar



I don't think this is what we want and I'm not sure if it's a maven
bug or not. Am I the only one having this nice 'feature'?

Felix
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.3 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGLe9p2lZVCB08qHERApwjAKCaqsXgwEEb13zcEKK1Bh/htgKhTgCdHOKr
tpv8B0IOP86i1YKHNyZX2+M=
=2eo8
-----END PGP SIGNATURE-----


Mime
View raw message