This is probably obvious but I think even if you were able to run the
version updates the release plugin will complain about having local
modifications. The updated pom would also need to be committed before the
m-release-p will be happy.
On Mar 4, 2011 5:33 AM, "nicolas de loof" <[email protected]> wrote:
> Hi,
>
> My project has dependencies on various common components, that have their
> own release lifecycle
> To get quicker bug-fixes and features we used to get them as SNAPSHOT, and
> when we plan a release we release first the commons, then the project.
>
> To do this, I need to upgrade my POM to switch snapshots to recent
released
> version, here is the workflow :
>
> * release common
> * upgrade POM to released commom
> * release the project
>
> I would like to automate the latest steps using
> versions:use-releases<
http://mojo.codehaus.org/versions-maven-plugin/use-releases-mojo.html>
> BUT using this one as a preparationGoal in release plugin fails, as the
> "Don't use SNAPSHOT" rule is checked by release plugin before the
> preparationGoal is executed.
>
> Do you have any suggestion on the way to do this ?
> Maybe I should create a Jira to change the release proces task order, so
> that the SNAPSHOT check occurs AFTER preparationGoal (makes sense to me,
but
> maybe this has some side-effects)
>
> Cheers,
> Nicolas
