Hi all, Something came in mind: instead of continue getting hurt by the mvn release-plugin, can't you switch over to a manual procedure? what I suggest:
* increase the version number in poms on /trunk, via MOJO's release-plugin <http://mojo.codehaus.org/versions-maven-plugin/> * tag the code; * increase the SNAPSHOT version number in poms on /trunk * checkout the tag; * deploy the site - pay attention on activating the gpg signatures That is what the release plugin does! Then close the staging repo only on Nexus and etc etc etc. Thoughts? all the best, -Simo http://people.apache.org/~simonetripodi/ http://simonetripodi.livejournal.com/ http://twitter.com/simonetripodi http://www.99soft.org/ On Fri, Apr 20, 2012 at 11:58 AM, Emmanuel Lécharny <[email protected]> wrote: > Le 4/20/12 11:32 AM, Francesco Chicchiriccò a écrit : > >> On 20/04/2012 11:27, Emmanuel Lécharny wrote: >>> >>> Hi guys, >>> >>> just to express my sympathy to Francesco who is fighting with Maven >>> while releasing :) >> >> Thanks Emmanuel!! >> It seems I am encountering http://jira.codehaus.org/browse/MRELEASE-679 >> I'll try to avoid pointless commits, for what possible... > > Hey, don't worry too much. Anyway, this is the best possible way to get your > total commit number very high. Release managers are some of the top > committers at The ASF for this reason ;) > > > > -- > Regards, > Cordialement, > Emmanuel Lécharny > www.iktek.com >
