http://mojo.codehaus.org/versions-maven-plugin/use-latest-releases-mojo.html
And why not just have Jenkins invoke 'mvn -B release:prepare
release:perform' directly? There's no need to use a custom Jenkins
plugin for this. Finally, updating these kinds of dependencies during
the actual release process seems to be not a good strategy. There are
all kinds of issues to consider and mitigate before doing something
like that, and frankly speaking, the person who is unaware of the
versions-m-p is unlikely to be able to consider them and therefore
mitigate them....
On Thu, Jul 24, 2014 at 12:29 PM, Jan Nehring
<jan.nehr...@semperlink.com> wrote:
> Hello Guys,
>
>
>
> we have a problem with maven releases and maven version plugin. In Jenkins
> we want to do releases automatically upon pressing a button. To remove
> snapshot dependencies we want to use the maven versions plugin. Suppose we
> have two projects A (latest release 0.0.1, latest snapshot 0.0.2-SNAPSHOT)
> and project B with a dependency on ProjectA - 0.0.2-SNAPSHOT and we want to
> release project B. How can we upgrade project Bs dependencies to the latest
> available release version? The maven versions plugin goal "use-releases"
> does not change the 0.0.2-SNAPSHOT dependency because there is no 0.0.2
> release version of this project.
>
>
>
> So my question is: how can we automatically remove snapshot dependencies and
> replace them with the latest available release version in our scenario?
>
>
>
> Best regards Jan
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
