On Sun, Jun 28, 2009 at 5:24 AM, Henri Yandell<flame...@gmail.com> wrote:
> The most important part to consider is 'What can go wrong?'. Ok, here's my reply to your question. Assuming that I am forced to follow the procedure as outlined by you. That means that I am forced not to use the maven-release-plugin. Consequently, I am forced to do a lot of manual steps, which would otherwise be completely automated. The likelyhood that something goes wrong would be dramatically increased, including production of invalid or corrupt artifacts at any stage in the process. I had my share of that and I don't want it any longer. And don't tell me anything about legal requirements. That was carefully discussed on legal@ in the thread on "Maven Releases" in April. The issues have been a lack of source distributions (which we at commons don't have, because we do and always did create source distributions), but the question of mutability or immutability of tags was no issue at all. Jochen -- Don't trust a government that doesn't trust you. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
