dependency and dependencymanagement - confusion

[kvenkatraman <ku...@gmail.com>]

I have project A and B. B is the child of A. So B Inherits properties and
dependencies of A.
If I have x version of dependency in A , same will be available for B also.

Then why do we need <dependencyManagement> , because by changing the version
of dependency in A will automatically availabe in B.

When dependency of A is avaliable in B due to inheritance , then why are we
required to call the parent dependency with <group-id>:<artifactid> for
managed dependency

I have searched a lot to question and i am still confused.

thanks in advance
kumar

-- 
View this message in context: http://www.nabble.com/dependency-and-dependencymanagement---confusion-tp20318920p20318920.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: dependency and dependencymanagement - confusion

[kvenkatraman <ku...@gmail.com>]

Thanks Matt . Now I am clear about dependencyManagement

Thanks
kumar
-- 
View this message in context: http://www.nabble.com/dependency-and-dependencymanagement---confusion-tp20318920p20356379.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: dependency and dependencymanagement - confusion

[Matthew Tordoff <ma...@markit.com>]

If you have additional dependencies in project B that aren't in A, and
those dependencies have an additional dependencies which are the same as
those in project A, but of a different version. Then you require
dependency management.

The best way to look at it is to see a tree of dependencies, each with
their own subdependencies. If at any point in that tree you have two
dependencies on the same component, however, with different versions,
you need to specify which version to use in preference.

Matt

-----Original Message-----
From: kvenkatraman [mailto:kumarve@gmail.com] 
Sent: 04 November 2008 09:35
To: users@maven.apache.org
Subject: dependency and dependencymanagement - confusion


I have project A and B. B is the child of A. So B Inherits properties
and dependencies of A.
If I have x version of dependency in A , same will be available for B
also.

Then why do we need <dependencyManagement> , because by changing the
version of dependency in A will automatically availabe in B.

When dependency of A is avaliable in B due to inheritance , then why are
we required to call the parent dependency with <group-id>:<artifactid>
for managed dependency

I have searched a lot to question and i am still confused.

thanks in advance
kumar

--
View this message in context:
http://www.nabble.com/dependency-and-dependencymanagement---confusion-tp
20318920p20318920.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




The content of this e-mail is confidential and may be privileged. It may be read, copied and used only by the intended recipient and may not be disclosed, copied or distributed. If you received this email in error, please contact the sender immediately by return e-mail or by telephoning +44 20 7260 2000, delete it and do not disclose its contents to any person. You should take full responsibility for checking this email for viruses. Markit reserves the right to monitor all e-mail communications through its network.
Markit and its affiliated companies make no warranty as to the accuracy or completeness of any information contained in this message and hereby exclude any liability of any kind for the information contained herein. Any opinions expressed in this message are those of the author and do not necessarily reflect the opinions of Markit.
For full details about Markit, its offerings and legal terms and conditions, please see Markit's website at http://www.markit.com <http://www.markit.com/> .

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