On 16/12/2011 16:15, Mark Thomas 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.
Jean-Frederic has informed me (via private e-mail) that he intends to fix this tomorrow. Despite that this change has already been made, I would like to see a discussion on whether or not switching to Nexus is in the best interests of the Tomcat project. I'll start a separate thread for that. Mark > >> 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. > >> Antonio >> >> P.S. Your project is a mess to be a Maven project. If you *really* want to >> move to Maven you need to do a major reconstruction of the directory >> structure. > > There are no plans to move Tomcat to use Maven for building. This is > purely about providing the Tomcat JARs as Maven artefacts in Maven > Central for others to use as they wish. > > Mark --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
