Martijn Dashorst wrote:
On 3/8/07, Al Maw <[EMAIL PROTECTED]> wrote:
Martijn Dashorst wrote:
The alternative is to write a little script which goes and updates
<version> elements in the POMs, tags everything in SVN, then does a
fresh checkout and then a "mvn -DperformRelease=true deploy" in each of
the jdk-1.* directories. This would actually be pretty simple. If it's
the preferred approach, I'll have a go at that. It'd be nice to be able
to do it with just Maven, though.
I think just doing a
svn cp branches/wicket-1.x tags/wicket-1.3.0
svn cp tags/wicket-1.x releases/wicket-1.3.0
svn switch releases/wicket-1.3.0
find . -name "pom.xml" | xargs sed -e
"s/version>1.x-incubating-SNAPSHOT/version>1.3.0-incubating-beta1/g"
mvn4 -DperformRelease=true install site assembly:assembly
mvn -DperformRelease=true install site assembly:assembly
svn commit -m "Release 1.3"
scp `find . -name "*.zip"`
people.apache.org:~/public_html/release-1.3-incubating-beta1
scp `find . -name "*.gz"`
people.apache.org:~/public_html/release-1.3-incubating-beta1
scp `find . -name "*.md5"`
people.apache.org:~/public_html/release-1.3-incubating-beta1
scp `find . -name "*.sig"`
people.apache.org:~/public_html/release-1.3-incubating-beta1
We can automate the scp stuff as part of the -DperformRelease=true.
We should surely also be copying doing a proper deploy, not an install,
so that we copy the JARs for the projects to apache's Maven repo, so
they can be synced up with repo1.maven.org?
I'm still in favour of using the release plug-in if we can, as it scps
the site to the right place, doesn't let you tag if there are test
failures, and all the rest of it.
We also need to sign the release using gpg, as I understand there is a
maven plugin for that as well.
OK, I'll see if I can look into this at some point.
Al
