It feels to me that UpdatePropertiesMojo has all the necessary code to implement that (the only difference is that it takes the latest and not the one from the remote pom). I am looking if I can hook that up
S. On Tue, Feb 4, 2014 at 12:33 PM, Stephane Nicoll <stephane.nic...@gmail.com>wrote: > SVN says it is pgier (Paul Gier). > > I am happy to implement it, I guess my question was more if this was left > off because it turned out to be a gigantic nightmare to implement. > > I'll have a look. > > Thanks, > S. > > > On Tue, Feb 4, 2014 at 11:18 AM, Stephen Connolly < > stephen.alan.conno...@gmail.com> wrote: > >> You'd need to dig out who originally contributed that goal... they might >> remember. I know it was a goal I didn't write >> >> >> On 4 February 2014 10:03, Stephane Nicoll <stephane.nic...@gmail.com>wrote: >> >>> Hi, >>> >>> I am looking at the versions-maven-plugin to force a build against a set >>> of "verified" dependencies. The idea is that a sub-project might declare >>> some older dependencies for backward-compat reason but we still want to >>> build the whole suite against a set of specific dependencies that would be >>> advertised as the one to use. >>> >>> Forcing the dependencies in a Maven project is not easy because it will >>> take the "closest" definition. But there might be a way using the >>> versions-maven-plugin compare-dependencies as it has the ability to modify >>> the POM itself. So we could run a build that would first update the >>> dependencies, run maven again against that modified dependency and then >>> cleanup the local change for the next build. >>> >>> The problem is that this goal has a 'updatePropertyVersions' that is >>> supposed to replace version in properties but the flag is used nowhere. >>> >>> Does anybody know why and do you think that sounds like a feasible >>> option? >>> >>> Thanks, >>> S. >>> >> >> >
