Hi Stephen, thanks - I'll investigate here.
Kind regards Andreas -----Original Message----- From: Stephen Connolly [mailto:[email protected]] Sent: Mittwoch, 16. Dezember 2009 11:34 To: Maven Users List Subject: Re: Reproducing a former build with exact dependencies but version ranges in the POM have a look at versions-maven-plugin it has some goals which might help you -Stephen 2009/12/16 Heix, Andreas <[email protected]> > Hi Anders, > > thanks - that's also the only thing I found. I just hoped for a more > flexible way to do it. So I'll have to dig deeper... > > Kind regards > Andreas > > -----Original Message----- > From: [email protected] [mailto:[email protected]] On > Behalf Of Anders Hammar > Sent: Mittwoch, 16. Dezember 2009 08:09 > To: Maven Users List > Subject: Re: Reproducing a former build with exact dependencies but version > ranges in the POM > > The only way (that I know of) to ensure a reproducable build is to lock > down > all versions in your pom. This includes plugins as well as dependencies. > > /Anders > > On Tue, Dec 15, 2009 at 10:48, Heix, Andreas <[email protected]> wrote: > > > Hi, > > > > for development we want to use dependency version ranges within our poms. > > As soon as we release a project for each artifact a certain version is > used > > in this build. At a later point in time we want to reproduce exactly the > > same build result without changing the poms which still contain version > > ranges. But very likely the content of our repositories will have > changed: > > meanwhile e.g. newer versions of certain artifacts are available. > > > > We can retrieve the list of used dependencies and plugins via mvn > > dependency:resolve & mvn dependency:resolve-plugins. > > Is there a chance to use this list as kind of 'whitelist'? It would > specify > > the exact versions of the dependencies instead of letting maven resolve > the > > "best fit" in future builds? > > > > Kind regards > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
