If I understand the request properly, "pinned versions" are
accomplished in Maven using <dependencyManagement/> as distinct from
<dependencies/>...
On Mon 12 Dec 2011 10:33:19 AM CST, Daz DeBoer wrote:
OK so "pinned versions" are a built-in feature of Maven? I can't seem
to find them documented anywhere.
I assume that dependency resolution fails if you have incompatible
pinned versions in different dependencies?
Is "pinning" just a narrower case of version ranges: as in does maven
fail if one dependency declares [1.0,2.0) and another declares "3.0"?
Actually I think I just answered my questions:
http://docs.codehaus.org/display/MAVEN/Dependency+Mediation+and+Conflict+Resolution#DependencyMediationandConflictResolution-DependencyVersionRanges
If there are any better docs on this I love the input.
In the past we've relied heavily on ivy's maven compatibility layer
for all of our maven integration. As we gradually replace this code
with our own implementations, we can start to address any of the
missing features.
Daz
On 11 December 2011 23:48, Robert Watkins <[email protected]
<mailto:[email protected]>> wrote:
Hi, Darrel - Wotif's still pretty much the same; we try and
improve it bit by bit, but that just means the problems keep
changing... ;)
The forced versions work, but only for the module they are
declared in. They don't work for modules that include the module
with the forced dependency - which means that if the particular
module is a lower-level infrastructure library (certainly is for
me), then the problem isn't solved.
Similarly, it's not mentioned in the generated maven pom.
Test output at:
http://dl.dropbox.com/u/46203904/gradle_dependency_results_2011_12_12.html
I'll have a look in the code and see what I can think of.
Robert.
On 10/12/2011, at 4:20 PM, Daz DeBoer wrote:
Hey Robert - how's Wotif?
Something similar ('forced versions') will be available in
Milestone 7, which should be released in the next few days. Check
out the documentation for the latest nightly:
http://gradle.org/releases/latest/docs/userguide/dependency_management.html
http://gradle.org/releases/latest/docs/dsl/org.gradle.api.artifacts.ResolutionStrategy.html
The support is still experimental. If it doesn't yet do what you
require, the implementation should give you a start.
We'd be very open to contributions :).
cheers
Daz
On 9 December 2011 17:42, Robert Watkins <[email protected]
<mailto:[email protected]>> wrote:
Hi all,
I've just raised a request for improvement for supporting
'pinned' versions. This is a subset of the larger version
range problem, where you express the version number like
this: [1.0]
See http://issues.gradle.org/browse/GRADLE-1992
This particular feature (or similar) is - for me - a
must-have before I can recommend adopting Gradle at work (I
work at Wotif.com <http://Wotif.com/>). We currently use
Maven, which works well enough, but is generally painful to
manage, especially on larger projects. Gradle shows
significant promise for being able to improve things a lot.
I'm willing to help implement this if someone can point out
where in the code base I should be looking.
--
"Software is too expensive to build cheaply"
Robert Watkins twitter: @twasink http://twasink.net/
[email protected] <mailto:[email protected]>
--
Darrell (Daz) DeBoer
Principal Engineer, Gradleware
http://www.gradleware.com <http://www.gradleware.com/>
--
Darrell (Daz) DeBoer
Principal Engineer, Gradleware
http://www.gradleware.com <http://www.gradleware.com/>
--
[email protected]
http://hibernate.org
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
