On Sat, 2009-07-18 at 10:40 -0700, Peter Niederwieser wrote: [ . . . ] > Maven has "RELEASE" and open version ranges (e.g. "[1.2,)"), but they don't > work as I expected them to. Better use a plain version number and enjoy a > reproducible build.
On the other hand I actually want to use the latest version of things
and will correct errors as they come up.
Also, tying builds to specific version leads to silly situation such as
using various plugins with Maven 2.0.10 and 2.1.0 where the plugin is
included by the Maven in use but depends on Maven 2.0.8 and so pulls
that in as well -- so in order to run Maven 2.1.0 you have to use Maven
2.0.8. This is just plain silly, but it is what happens :-(
I still like the idea of saying "use the version of X you can find here
<path>", but Maven and Gradle don't seem to support that.
--
Russel.
=============================================================================
Dr Russel Winder Partner
xmpp: [email protected]
Concertant LLP t: +44 20 7585 2200, +44 20 7193 9203
41 Buckmaster Road, f: +44 8700 516 084 voip: sip:[email protected]
London SW11 1EN, UK m: +44 7770 465 077 skype: russel_winder
signature.asc
Description: This is a digitally signed message part
