maven-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Baptiste MATHUS ...@batmat.net>
Subject Re: How to use the latest version from dependencies (not from all repository)
Date Sat, 06 Aug 2011 16:53:08 GMT
2011/8/6 Ron Wheeler <rwheeler@artifact-software.com>

> On 06/08/2011 11:47 AM, boraldo wrote:
>
>> I am absolutely agree with your opinion that unreproducability of build is
>> a
>> bad feature, but ...
>>
>> 1. Maven has a built-in mechanism of dependency version range
>> (http://docs.codehaus.org/**display/MAVEN/Dependency+**
>> Mediation+and+Conflict+**Resolution#**DependencyMediationandConflict**
>> Resolution-**DependencyVersionRanges<http://docs.codehaus.org/display/MAVEN/Dependency+Mediation+and+Conflict+Resolution#DependencyMediationandConflictResolution-DependencyVersionRanges>
>> ).
>> Using this you can set that the build will always include the last version
>> of some artifact. That makes it absolutely unreproducable. So
>> unreproducability doesn't contradict with the concepts of Maven and what I
>> ask could be possible in it too.
>>
> Just because Maven can do something does not make it a good idea.
> Maven will give you enough rope to hang yourself and there enough really
> brilliant people here who can show you how to make the killer knot, so that
> it is easy to get hurt.
> Just read some of the threads on version range or worse yet - profiles if
> you want to see people getting into serious trouble.


+1. Version ranges is evil.
Maven is designed to help you ensure build reproducibility.

Using undefined versions is exactly the opposite.

Bump your versions regularly, script it if you like, but don't use version
ranges.

Cheers.

-- 
Baptiste <Batmat> MATHUS - http://batmat.net
Sauvez un arbre,
Mangez un castor !
nbsp;!

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message