On 3/8/07, Al Maw <[EMAIL PROTECTED]> wrote:
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?
Incubator jars are barred from being released to the central repo. And
the release should be voted on before we put it into the wild. Maven
does have something like a staging thing, not sure how that works.
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 will not deploy the site as it currently is: no more examples and
just the default maven reports. But having the javadoc and the
dependencies up on the site is something worthwile. The WICKETxSITE
will function as our site portal, wicket-1.3.0 will have the release
details.
> 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.
I just got gpg installed on my mac, so I'll be able to generate a key
and sign the releases.
Martijn
--
Learn Wicket at ApacheCon Europe: http://apachecon.com
Join the wicket community at irc.freenode.net: ##wicket
Wicket 1.2.5 will keep your server alive. Download Wicket now!
http://wicketframework.org
