Hi Marko,
On Sep 26, 2008, at 12:20 PM, Marko Bauhardt wrote:
Hi,
i have a question about the dependency management in gradle.
maven supports two types of dependencies. one is the normal
"dependency" tag. And another way to define dependencies for
multiprojects is to use the "dependencyManagement".
See http://maven.apache.org/guides/introduction/introduction-to-
dependency-mechanism.html#Dependency_Management
I think the different between dependency and dependencyManagement
is that a sub-module inherit the dependency definitions like
"exclude" or "version" from the parent-project. But only if this
dependency is configured in the sub-module.
Is there a way how gradle / ivy deals with "dependencyManagement" ?
After doing some research to answer this question I found a new
feature in Ivy which is supposed to enable this. It is not documented
yet in the Ivy doc.
There is some description in the related issue: https://
issues.apache.org/jira/browse/IVY-784
Could you file an issue for exposing this via Gradle?
You can also use the force attribute in your Gradle dependency
declaration to make a certain version win.
- Hans
--
Hans Dockter
Gradle Project lead
http://www.gradle.org
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
