On 25 March 2010 17:40, David Jencks <[email protected]> wrote: > I already said this on march 1 but there was more stuff in that email so > maybe everyone missed it and I could be considerably more explicit. > > DON"T try to use the root pom to release anything and don't try to release > it. It's only there for convenience. Judging by the recent posts I think it > causes a lot more trouble than it is worth and should be removed. > > I don't know the exact order to release subprojects in. Someone will have to > figure it out. You can't release in the wrong order because there will be > snapshots which will fail the build. I'm pretty sure it starts: > > - parent > -eba-maven-plugin
yes, and using mvn dependency:tree a valid order would be: testsupport util blueprint jndi transaction web application jmx jpa spi-fly (which we're not releasing) samples > > For each subproject run: > > mvn versions:use-releases > svn commit -m "updated to latest releases" > mvn release:prepare -Papache-release > mvn release:perform -Papache-release > > The first two steps should be unnecessary for the parent pom. > > The versions plugin will find the release candidates from earlier subprojects > and update the poms to use them instead of the snapshots. > > > thanks > david jencks > >
