On 22 Dec 06, at 11:18 PM 22 Dec 06, Brett Porter wrote:
Hi,
I was pretty confused by the state of the plugin process, and just
wanted to check:
- should the "remote resources" plugin be in the main
configuration, rather than profiles? It makes sense for all plugin
deployments to have that, and is less error prone
Once I'm done testing it and there are three more releases I'll be
doing this weekend.
- if not, should the release plugin configure itself to add that
profile?
The remote resources setup should be pushed up for anyone at apache
doing releases. It seems to be working from Joakim's account, for the
Geronimo releases and the few that I've done so far.
- what is left to do to make the staging usable?
Test the copying tool which I've done for file:/// based urls. There
is a bug in Wagon which prevents it from working on scp:// based
urls. Joakim will look at that later.
- is any docs started on this somewhere?
It's really just setting up your profile, using it and it will be
passed along in the release plugin when it picks up the active profiles:
http://svn.apache.org/repos/asf/maven/release/trunk/releasing.apt
The remote resources stuff works fine, the staging has only been
tried once. I would stick with just using the remote resources
profile with a standard release for your release and when I've tested
the staging using Tom's copier I'll document that for the standard
process incorporating John's release report.
Using the "remoteResources" profile with what you're used to will
work for your plugin release.
Jason.
Thanks,
Brett
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
