Yes, that would be the ideal solution. In the meantime, I'm avoiding manual and error-prone work by putting the process into a shell script.
Best regards, Eric > -----Ursprüngliche Nachricht----- > Von: Stephen Duncan Jr [mailto:[email protected]] > Gesendet: Freitag, 11. September 2009 15:57 > An: Maven Users List > Betreff: Re: How to update parent during release:prepare > > I certainly have the exact same problem. And using the > versions plugin only > helps somewhat in partially automating what I currently do > manually. Last > time I made the mistake of not manually changing the parent > version, the > release plugin, I believe, offered to update to a released > version, but > didn't actually change it, resulting in what was essentially a broken > release (since it had a SNAPSHOT parent). Similarly I face > problems with > the release plugin not handling SNAPSHOT versions of > "dependencies" declared > outside the dependencies section (typically using the maven-dependency > plugin instead). I would like to see the release plugin > updated to handle > these rather than work around them with the versions plugin. > > -Stephen > > On Fri, Sep 11, 2009 at 9:51 AM, Lewis, Eric > <[email protected]> wrote: > > > Thanks, that works well! > > > > However, I'm still wondering whether I'm the only one > releasing that way. > > It seems to me that the release plugin can only be used > together with the > > versions plugin. > > I think that most developers have some sort of company-wide > parent POM > > which they refer to, and when releasing, they probably all > have the same > > problem as I do. > > > > Best regards, > > Eric > > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
