Hello Marshall
Can you confirm the values of Ok set for checkpoint.check-in-development-version as in
checkpoint.check-in-development-version=OK
in release.properties file?
thanks,
Martin Gainty
______________________________________________
Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité
Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten
wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist
unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet
keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen
wir keine Haftung fuer den Inhalt uebernehmen.
Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le destinataire
prévu, nous te demandons avec bonté que pour satisfaire informez l'expéditeur. N'importe
quelle diffusion non autorisée ou la copie de ceci est interdite. Ce message sert à l'information
seulement et n'aura pas n'importe quel effet légalement obligatoire. Étant donné que les
email peuvent facilement être sujets à la manipulation, nous ne pouvons accepter aucune
responsabilité pour le contenu fourni.
> Date: Mon, 1 Nov 2010 12:26:27 -0400
> From: msa@schor.com
> To: users@maven.apache.org
> CC: dev@uima.apache.org
> Subject: maybe bug in release plugin for computing next dev release?
>
> I have a pom which has a property which has as a value "2.3.1-SNAPSHOT".
>
> The property is used to factor into one spot the version level for dependencies,
> where the dependencies are for other modules in a multi-module build (most of
> which have the same
> version level).
>
> When I do mvn release:prepare -DdryRun on a POM which includes this as a module,
> the release:prepare successfully updates the property, first, to "2.3.1" for the
> "tag", and then, for the next development version, to "2.3.2-SNAPSHOT". I think
> it figures out that this property is being used as a dependency version value,
> and matches it to version levels of things in the "Reactor", to figure out it
> needs updating.
>
> So far everything seems to be correct.
>
> But, if I do exactly the same thing, but leave off the "-DdryRun", it updates
> the property, first (as before), to "2.3.1" for the tag, but then does *not*
> update it for the next development version.
>
> Any idea why? Is this a (known) bug? I can, of course, work around this by
> manually updating this property to the right level and committing that change to
> the trunk.
>
> -Marshall Schor
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>