Use Subversion 1.5
the release plugin is broken with svn 1.5 and will not make a release if the
entire workspace is not 100% up to date
;-)
(may be fixed in svn 1.5.4)
2008/12/9 sverhagen <[EMAIL PROTECTED]>
>
> Hi. We heavily use the Maven release plugin.
> Following scenario:
> * Developers update from SVN
> * Developer 1 commits a change
> * Developer 2 commits a change and releases ("mvn release:prepare")
>
> Because developer 2 does not explicitly update from SVN, the change from
> developer 1 will not be in the release. Hard to track down, hard to detect.
>
> I've attempted adding stategies to check if the releasing developer
> (developer 2) is up-to-date, using buildnumber-maven-plugin. Unsuccessful,
> since release plugin does its own local modifications prior to running the
> buildnumber plugin.
>
> I know I can make a nice shell script to check this, but I would like to
> configure it in Maven, to make things mandatory and reproducible.
>
> Thanks for your ideas!
>
> Sander.
> --
> View this message in context:
> http://www.nabble.com/Up-to-date-release-tp20925759p20925759.html
> Sent from the Maven - Users mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
