Hi,
The dependencyManagement section defines the default dependency information
for use in a group of POMs. It provides a way to specify a "standard"
version for a particular dependency.
Please note there are two important points to make it useful.
1) The dependency defined under dependencyManagement is not used unless it
is referenced in a pom.xml within the group.
2) You can override the default by explicitly setting the attribute (such as
version) in a pom.xml within the group.
Based on the information above, I personally prefer to use
"dependencyManagment".
Thanks,
Raymond
----- Original Message -----
From: "Jim Marino" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Monday, November 06, 2006 12:17 PM
Subject: Re: Java SCA dependency versions listed in various pom.xmls
For things that needs to stay in sync, I agree having one place to
specify things is probably beneficial. Not being a Maven person, I'm
unsure of the Maven convention for this... One thing we need to be
careful about, though, is not over-specifying. For example, if two
orthogonal extensions are dependent on StAX, they should not share a
common version.
Jim
On Nov 6, 2006, at 11:47 AM, Rick wrote:
Hello,
Currently there are identical artifact dependencies listed throughout
the SCA Java maven hierarchy that can be changed to different versions
either intentionally or accidentally. For example axis2-kernel is
specified in two levels of maven pom.xml At the sca level there is
dependencyManagement element that uses the axis2Version property and
there is also a reference in sca/ tools/pom.xml that is hard coded to
SNAPSHOT. This brings about the following questions:
Is this a good practice? I this weekend changed one and didn't catch the
other so my opinion is no, I think until the need arises that they
require to be different this should be set in one place.
If we agree what's the best solution? Use maven property values to keep
them in sync, or just list the version at the top level (sca/ pom.xml)
under the dependencyManagement?
If we take the latter approach, do we list ALL external dependencies
there to be consistent?
If we feel this should change should we still do this for M2 release?
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
