You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by Niall Pemberton <ni...@gmail.com> on 2008/02/25 16:29:35 UTC
[all] commons-parent pom release
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).
Also I only just noticed that the compiler plugin configuration moved
from the "build\plugins" section to "build\plugins\pluginManagement" -
not sure what the reason for that was, but I guess thats my lack of
understanding
http://svn.apache.org/viewvc?view=rev&revision=613456
I'll leave this at least a couple of days to see what kind of
discussion evolves before starting a vote on commons-parent-8
Niall
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [all] commons-parent pom release
Posted by James Carman <ja...@carmanconsulting.com>.
On 2/26/08, Dennis Lundberg <de...@apache.org> wrote:
> It has been used internally by the Maven developers for quite some time
> now. The main purpose is to move artifacts from a staging repository to
> the real repository.
>
> A staging repo, usually put in a user's home directory on people, is
> used for staging a release. From there is will be checked by the pmc and
> other interested parties.
>
I like this idea. I tinkered with the idea of having m2 "deploy" my
artifacts to a dummy repository inside my home directory on
people.apache.org, by overriding the deployment settings in the "rc"
profile. But, I ended up doing it manually because I wanted
everything to live in a directory name suffixed by the release
candidate number (rc4 for example). Subsequent deployments would
actually overwrite the previous release candidate's artifacts and I
wasn't too sure that was the right thing to do.
> If the release is deemed fit for public consumption, the stage-plugin is
> used to copy the artifacts from the staging repo to the apache
> repository-sync-directory.
>
> It helps people who want to use Maven 2 as the build tools and at the
> same time being able to vote on the actual bits of a release.
>
> --
>
> Dennis Lundberg
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [all] commons-parent pom release
Posted by Dennis Lundberg <de...@apache.org>.
simon.kitching@chello.at wrote:
> Niall Pemberton schrieb:
>> On Mon, Feb 25, 2008 at 4:55 PM, James Carman
>> <ja...@carmanconsulting.com> wrote:
>>
>>> On 2/25/08, Niall Pemberton <ni...@gmail.com> wrote:
>>> > On Mon, Feb 25, 2008 at 3:36 PM, James Carman
>>> > <ja...@carmanconsulting.com> wrote:
>>> > > On 2/25/08, Niall Pemberton <ni...@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
It has been used internally by the Maven developers for quite some time
now. The main purpose is to move artifacts from a staging repository to
the real repository.
A staging repo, usually put in a user's home directory on people, is
used for staging a release. From there is will be checked by the pmc and
other interested parties.
If the release is deemed fit for public consumption, the stage-plugin is
used to copy the artifacts from the staging repo to the apache
repository-sync-directory.
It helps people who want to use Maven 2 as the build tools and at the
same time being able to vote on the actual bits of a release.
--
Dennis Lundberg
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [all] commons-parent pom release
Posted by Niall Pemberton <ni...@gmail.com>.
On Tue, Feb 26, 2008 at 12:13 PM, simon.kitching@chello.at
<si...@chello.at> wrote:
> Niall Pemberton schrieb:
>
>
> > On Mon, Feb 25, 2008 at 4:55 PM, James Carman
> > <ja...@carmanconsulting.com> wrote:
> >
> >> On 2/25/08, Niall Pemberton <ni...@gmail.com> wrote:
> >> > On Mon, Feb 25, 2008 at 3:36 PM, James Carman
> >> > <ja...@carmanconsulting.com> wrote:
> >> > > On 2/25/08, Niall Pemberton <ni...@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..
Only looked at the docs:
http://maven.apache.org/plugins/maven-stage-plugin/copy-mojo.html
Theres just one goal to copy from one maven repo to another.
Niall
> Regards, Simon
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [all] commons-parent pom release
Posted by "simon.kitching@chello.at" <si...@chello.at>.
Niall Pemberton schrieb:
> On Mon, Feb 25, 2008 at 4:55 PM, James Carman
> <ja...@carmanconsulting.com> wrote:
>
>> On 2/25/08, Niall Pemberton <ni...@gmail.com> wrote:
>> > On Mon, Feb 25, 2008 at 3:36 PM, James Carman
>> > <ja...@carmanconsulting.com> wrote:
>> > > On 2/25/08, Niall Pemberton <ni...@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
Re: [all] commons-parent pom release
Posted by Niall Pemberton <ni...@gmail.com>.
On Tue, Feb 26, 2008 at 12:35 PM, James Carman
<ja...@carmanconsulting.com> wrote:
> On 2/26/08, Niall Pemberton <ni...@gmail.com> wrote:
> > 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?
>
> You're right. It's really not that big of a benefit. But, it does
> save at least one step (in a somewhat daunting process for the newbies
> like me). I wish we could just issue one command and have the site
> deployed where it's supposed to go and the distribution files built,
> signed, checksummed (is that a word?), and copied to where they're
> supposed to go. Now that would be automation! :)
OK so lets leave this for the moment and get version 8 of
commons-parent out. We definetly need to improve this with at a
minimum good docs - perhaps would be good to discuss at ApacheCon,
hopefully with some maven gurus around.
Niall
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [all] commons-parent pom release
Posted by James Carman <ja...@carmanconsulting.com>.
On 2/26/08, Niall Pemberton <ni...@gmail.com> wrote:
> 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?
You're right. It's really not that big of a benefit. But, it does
save at least one step (in a somewhat daunting process for the newbies
like me). I wish we could just issue one command and have the site
deployed where it's supposed to go and the distribution files built,
signed, checksummed (is that a word?), and copied to where they're
supposed to go. Now that would be automation! :)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [all] commons-parent pom release
Posted by Niall Pemberton <ni...@gmail.com>.
On Mon, Feb 25, 2008 at 4:55 PM, James Carman
<ja...@carmanconsulting.com> wrote:
> On 2/25/08, Niall Pemberton <ni...@gmail.com> wrote:
> > On Mon, Feb 25, 2008 at 3:36 PM, James Carman
> > <ja...@carmanconsulting.com> wrote:
> > > On 2/25/08, Niall Pemberton <ni...@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?
Niall
> >
> > Niall
> >
> >
> > > > Also I only just noticed that the compiler plugin configuration moved
> > > > from the "build\plugins" section to "build\plugins\pluginManagement" -
> > > > not sure what the reason for that was, but I guess thats my lack of
> > > > understanding
> > > > http://svn.apache.org/viewvc?view=rev&revision=613456
> > > >
> > > > I'll leave this at least a couple of days to see what kind of
> > > > discussion evolves before starting a vote on commons-parent-8
> > > >
> > > > Niall
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [all] commons-parent pom release
Posted by James Carman <ja...@carmanconsulting.com>.
On 2/25/08, Niall Pemberton <ni...@gmail.com> wrote:
> On Mon, Feb 25, 2008 at 3:36 PM, James Carman
> <ja...@carmanconsulting.com> wrote:
> > On 2/25/08, Niall Pemberton <ni...@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).
>
>
> Niall
>
>
> > > Also I only just noticed that the compiler plugin configuration moved
> > > from the "build\plugins" section to "build\plugins\pluginManagement" -
> > > not sure what the reason for that was, but I guess thats my lack of
> > > understanding
> > > http://svn.apache.org/viewvc?view=rev&revision=613456
> > >
> > > I'll leave this at least a couple of days to see what kind of
> > > discussion evolves before starting a vote on commons-parent-8
> > >
> > > Niall
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> > > For additional commands, e-mail: dev-help@commons.apache.org
> > >
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> > For additional commands, e-mail: dev-help@commons.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [all] commons-parent pom release
Posted by Niall Pemberton <ni...@gmail.com>.
On Mon, Feb 25, 2008 at 3:36 PM, James Carman
<ja...@carmanconsulting.com> wrote:
> On 2/25/08, Niall Pemberton <ni...@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"?
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
Niall
> > Also I only just noticed that the compiler plugin configuration moved
> > from the "build\plugins" section to "build\plugins\pluginManagement" -
> > not sure what the reason for that was, but I guess thats my lack of
> > understanding
> > http://svn.apache.org/viewvc?view=rev&revision=613456
> >
> > I'll leave this at least a couple of days to see what kind of
> > discussion evolves before starting a vote on commons-parent-8
> >
> > Niall
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> > For additional commands, e-mail: dev-help@commons.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [all] commons-parent pom release
Posted by James Carman <ja...@carmanconsulting.com>.
On 2/25/08, Niall Pemberton <ni...@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?
>
> Also I only just noticed that the compiler plugin configuration moved
> from the "build\plugins" section to "build\plugins\pluginManagement" -
> not sure what the reason for that was, but I guess thats my lack of
> understanding
> http://svn.apache.org/viewvc?view=rev&revision=613456
>
> I'll leave this at least a couple of days to see what kind of
> discussion evolves before starting a vote on commons-parent-8
>
> Niall
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org