On 20 August 2011 10:45, Ansgar Konermann <[email protected]> wrote: > > Am 20.08.2011 11:37 schrieb "Tim Pizey" <[email protected]>: >> >> Hi, >> >> I see from >> https://cwiki.apache.org/MAVEN/maven-3x-compatibility-notes.html#Maven3.xCompatibilityNotes-PluginMetaversionResolution >> >> Plugin Metaversion Resolution >> Internally, Maven 2.x used the special version markers RELEASE and >> LATEST to support automatic plugin version resolution. These >> metaversions were also recognized in the <version> element for a >> <plugin> declaration. For the sake of reproducible builds, Maven 3.x >> no longer supports usage of these metaversions in the POM. As a >> result, users will need to replace occurrences of these metaversions >> with a concrete version. >> >> What is the right way now to cover the developers use case where I >> want to discover and use the latest version of everything, >> see what breaks, fix and upgrade to latest. > > One option is to use maven-version-plugin to update dependency/parent > versions, potentially on a branch dedicated for this purpose, run mvn clean > verify on your ci server for this branch and see if/what breaks. If all your > tests are still green, merge the poms of this branch into your main line. If > you preferr one single development line, omit the dedicated branch. >
Great, thanks Ansgar cheers Tim -- Tim Pizey - http://pizey.net/~timp Centre for Genomics and Global Health - http://cggh.org --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
