commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "simon.kitching@chello.at" <simon.kitch...@chello.at>
Subject Re: [all] commons-parent pom release
Date Tue, 26 Feb 2008 12:13:15 GMT
Niall Pemberton schrieb:
> On Mon, Feb 25, 2008 at 4:55 PM, James Carman
> <james@carmanconsulting.com> wrote:
>   
>> On 2/25/08, Niall Pemberton <niall.pemberton@gmail.com> wrote:
>>  > On Mon, Feb 25, 2008 at 3:36 PM, James Carman
>>  >  <james@carmanconsulting.com> wrote:
>>  >  > On 2/25/08, Niall Pemberton <niall.pemberton@gmail.com> wrote:
>>  >  >  > I would like to do a release of commons-parent mainly for the OSGi
>>  >  >  >  (i.e. bundle) plugin and commons-build-plugin - the full set of
>>  >  >  >  changes are here:
>>  >  >  >
>>  >  >  >  http://svn.apache.org/viewvc/commons/proper/commons-parent/trunk/pom.xml?r1=630871&r2=611431&diff_format=h
>>  >  >  >
>>  >  >  >  I know James had a couple of proposals (adding site deployment
and
>>  >  >  >  assembly plugin to "rc" profile) - but I'm not sure about them
ATM
>>  >  >  >  (adding the assembly plugin messes up anything that doesn't have
an
>>  >  >  >  assembly - e.g. commons-parent).
>>  >  >
>>  >  >  Can we at least add in the deployment directory stuff for the site?
>>  >  >  The only problem with that is that you need to supply a property
>>  >  >  ("rcNumber") when you run in order for it to properly construct the
>>  >  >  URL.  Does anyone know an easy way to grab the name of the SVN tag
>>  >  >  during the build so that we could use that?
>>  >
>>  >
>>  > How do you use this - something like "mvn site:stage"?
>>
>>  Actually, it changes the default site deployment location.  So, all
>>  you have to do is:
>>
>>  mvn -Prc site:deploy
>>
>>
>>  >
>>  >  Also does it give much benefit over just zipping up the site and
>>  >  uploading manually? I can see us having to keep educating RM's that
>>  >  they need to specify the "releaseManager" and "rc version" either on
>>  >  the command line or in their settings.xml
>>  >
>>
>>  We just need a nice document (currently in the works) that
>>  specifically spells out the exact steps (with maven/SVN commands).
>>     
>
> OK but I still don't see much benefit - if I'm creating a release
> candidate I have to zip up the artifacts and upload them to
> p.a.o/~niallp so no big deal to include the site as well. My
> preference is to keep it simple and I can't see me using this. I guess
> its not a big deal to include it, but does anyone else think its a
> good idea?
>   
Does anyone know what the very-recently-released maven-stage-plugin does?
It's meant to be used for staging releases, but apart from that I
haven't looked into it..

Regards, Simon


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org


Mime
View raw message