maven-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From lukewpatterson <lukewpatter...@gmail.com>
Subject Re: Some questions about "grouped dependencies"
Date Wed, 17 Feb 2010 13:16:02 GMT


Anders Hammar wrote:
> 
> a) This is the limitation/drawback of grouped dependencies. The
> dependencies
> you get through a grouped dependencies will be a level down (actually they
> will be transient deps).
> 

The description in "grouping dependencies" should probably be changed then
from:
"You can now add this project as a dependency and all of its dependencies
will be added to your project."
to:
"You can now add this project as a dependency and all of its dependencies
will be added as transitive dependencies to your project."

On a related note, consider:

from "Maven By Example" book:
"A good rule of thumb in Maven is to always declare explicit dependencies
for classes referenced in your code." [1]
That seems to contradict "Maven: The Complete Reference" book when it places
"grouping dependencies" in the "Best Practices" section.


It seems that composition has some major drawbacks compared to inheritance.


[1]
http://www.sonatype.com/books/mvnex-book/reference/optimizing-sect-dependency-plugin.html

-- 
View this message in context: http://old.nabble.com/Some-questions-about-%22grouped-dependencies%22-tp27615566p27623469.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


Mime
View raw message