On 16/12/2011 19:38, sebb wrote: > On 16 December 2011 16:15, Mark Thomas <ma...@apache.org> wrote: >> On 16/12/2011 16:06, Antonio Petrelli wrote: >>> Please Mark calm down. >> >> No, I will not calm down. The release process has been changed without >> prior discussion and on top of that it is now broken for Maven >> artefacts. That is not acceptable. >> >>> Being possible to deploy to Nexus does not mean that the project is >>> configured to do that. >> >> Exactly. Tomcat has been using scp+rsync via people.a.o for several >> years. That process has been broken by the switch to Nexus. >> >>> To enable this, you need to configure the needed POM >>> metadata (SCM, website) and let the master POM of Tomcat be child of the >>> Apache Master pom. >>> Even if you have done this steps, if you are not using the Maven release >>> plugin, it does not work. AFAICT you should be able to (temporarily, for >>> good) deploy to people.a.o. >> >> The whole point is that we can no longer release via people.a.o because >> of the switch to Nexus. It has been made quite clear that a project can >> use either Nexus or people.a.o but not both. For Tomcat to use Nexus, >> the Tomcat release scripts need to be updated and they have not been. > > That's not how Nexus is being used in Commons - but I don't know what > has been set up here, so perhaps the following is not applicable:
It isn't. We are talking about the release process for Maven artefacts. Mark --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
