I had a small discussion with Tamas on IRC yesterday about this, and I
did come to realize that the proper way to do this is to do a regular
release of maven-archiver 2.4.2, then make a branch in svn for
maven-jar-plugin 2.3.2. On the branch, update to maven-archiver 2.4.2
and then release from the branch. In that way the build never breaks and
CI does not need any staging dependencies.
In retrospect I did the next-best thing, which was a temporary revert of
the upgrade on trunk. So I can procastinate/fear svn branches for a
little longer ;)
Kristian
Den 18.08.2011 16:08, skrev Kristian Rosenvold:
By staging a dual release of maven-archiver and maven-jar-plugin. So now
you have 3 days to fix the adding of
https://repository.apache.org/content/groups/staging/ or whatever to
hudson ;)
Kristian
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
