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]> 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). 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]
>
>
--
Darrell (Daz) DeBoer
Principal Engineer, Gradleware
http://www.gradleware.com
