[parent] Staging releases

classic Classic list List threaded Threaded
7 messages Options
Reply | Threaded
Open this post in threaded view
|

[parent] Staging releases

Rahul Akolkar
How is everyone staging m2 releases? Can we apply the following patch
to commons-parent? Please try to read over any formatting mishaps --
its the (release profile)/distributionManagement/repository element.


Index: pom.xml
===================================================================
--- pom.xml (revision 638493)
+++ pom.xml (working copy)
@@ -378,9 +378,9 @@
       <id>release</id>
       <distributionManagement>
         <repository>
-          <id>apache.releases</id>
-          <name>Apache Release Distribution Repository</name>
-          <url>${commons.deployment.protocol}://people.apache.org/www/people.apache.org/repo/m2-ibiblio-rsync-repository</url>
+          <id>commons.staging</id>
+          <name>Apache Commons Staging Repository</name>
+          <url>${commons.deployment.protocol}://people.apache.org/builds/commons/${commons.componentid}/${pom.version}/m2-staging-repository/</url>
         </repository>
       </distributionManagement>
       <build>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [parent] Staging releases

Torsten Curdt
I usually using / in favor of...

${commons.deployment.protocol}://people.apache.org/home/${user}/somepath

...and after release that gets moved into the correct place in the m2 repo.

cheers
--
Torsten

On 3/19/08, Rahul Akolkar <[hidden email]> wrote:

> How is everyone staging m2 releases? Can we apply the following patch
>  to commons-parent? Please try to read over any formatting mishaps --
>  its the (release profile)/distributionManagement/repository element.
>
>
>  Index: pom.xml
>  ===================================================================
>  --- pom.xml     (revision 638493)
>  +++ pom.xml     (working copy)
>  @@ -378,9 +378,9 @@
>        <id>release</id>
>        <distributionManagement>
>          <repository>
>  -          <id>apache.releases</id>
>  -          <name>Apache Release Distribution Repository</name>
>  -          <url>${commons.deployment.protocol}://people.apache.org/www/people.apache.org/repo/m2-ibiblio-rsync-repository</url>
>  +          <id>commons.staging</id>
>  +          <name>Apache Commons Staging Repository</name>
>  +          <url>${commons.deployment.protocol}://people.apache.org/builds/commons/${commons.componentid}/${pom.version}/m2-staging-repository/</url>
>          </repository>
>        </distributionManagement>
>        <build>
>
>  ---------------------------------------------------------------------
>  To unsubscribe, e-mail: [hidden email]
>  For additional commands, e-mail: [hidden email]
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

RE: [parent] Staging releases

Jörg Schaible-2
Torsten Curdt wrote:
> I usually using / in favor of...
>
> ${commons.deployment.protocol}://people.apache.org/home/${user
> }/somepath
>
> ...and after release that gets moved into the correct place in the m2
> repo.

... and then the metadata is wrong, i.e. does no longer contain all the old releases.

- Jörg

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [parent] Staging releases

Torsten Curdt

On Mar 20, 2008, at 10:40 AM, Jörg Schaible wrote:

> Torsten Curdt wrote:
>> I usually using / in favor of...
>>
>> ${commons.deployment.protocol}://people.apache.org/home/${user
>> }/somepath
>>
>> ...and after release that gets moved into the correct place in the m2
>> repo.
>
> ... and then the metadata is wrong, i.e. does no longer contain all  
> the old releases.

Huh??? This should just affect the place the build is deployed to.


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [parent] Staging releases

Wendy Smoak
In reply to this post by Jörg Schaible-2
On Thu, Mar 20, 2008 at 2:40 AM, Jörg Schaible
<[hidden email]> wrote:
> Torsten Curdt wrote:

>  > ...and after release that gets moved into the correct place in the m2
>  > repo.
>
>  ... and then the metadata is wrong, i.e. does no longer contain all the old releases.

True.  The Maven Stage Plugin is meant to help with this:
http://maven.apache.org/plugins/maven-stage-plugin/usage.html

--
Wendy

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [parent] Staging releases

Rahul Akolkar
In reply to this post by Torsten Curdt
On 3/20/08, Torsten Curdt <[hidden email]> wrote:
> I usually using / in favor of...
>
>  ${commons.deployment.protocol}://people.apache.org/home/${user}/somepath
>
<snip/>

That'd work too, if we can all agree on the somepath fragment (I don't
want to make that call for everyone, other than it begin with
public_html :-). Moreover, I've used pao/builds for this sort of thing
before, so I gravitate to that. Just had a look again, seems to be a
popular stage for (some parts of, formerly) Maven land [1] and various
[2] other [3] places [4].

Couple of updates to my proposed pattern below:

 * I think the m2-staging-repository fragment can just go, or atleast
be shorter like m2-staged or something

 * Given the way we do releases (multiple RCs), it makes sense to
replace the ${pom.version} fragment with
${pom.version}-${commons.rc.version} at the risk of inventing a new
property.

-Rahul

[1] http://people.apache.org/builds/maven/
[2] http://people.apache.org/builds/struts/
[3] http://people.apache.org/builds/shale/
[4] http://people.apache.org/builds/myfaces/


>  ...and after release that gets moved into the correct place in the m2 repo.
>
>  cheers
>  --
>  Torsten
>
>
>  On 3/19/08, Rahul Akolkar <[hidden email]> wrote:
>  > How is everyone staging m2 releases? Can we apply the following patch
>  >  to commons-parent? Please try to read over any formatting mishaps --
>  >  its the (release profile)/distributionManagement/repository element.
>  >
>  >
>  >  Index: pom.xml
>  >  ===================================================================
>  >  --- pom.xml     (revision 638493)
>  >  +++ pom.xml     (working copy)
>  >  @@ -378,9 +378,9 @@
>  >        <id>release</id>
>  >        <distributionManagement>
>  >          <repository>
>  >  -          <id>apache.releases</id>
>  >  -          <name>Apache Release Distribution Repository</name>
>  >  -          <url>${commons.deployment.protocol}://people.apache.org/www/people.apache.org/repo/m2-ibiblio-rsync-repository</url>
>  >  +          <id>commons.staging</id>
>  >  +          <name>Apache Commons Staging Repository</name>
>  >  +          <url>${commons.deployment.protocol}://people.apache.org/builds/commons/${commons.componentid}/${pom.version}/m2-staging-repository/</url>
>  >          </repository>
>  >        </distributionManagement>
>  >        <build>
>  >

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [parent] Staging releases

Rahul Akolkar
In reply to this post by Wendy Smoak
On 3/20/08, Wendy Smoak <[hidden email]> wrote:

> On Thu, Mar 20, 2008 at 2:40 AM, Jörg Schaible
>  <[hidden email]> wrote:
>
> > Torsten Curdt wrote:
>
>  >  > ...and after release that gets moved into the correct place in the m2
>  >  > repo.
>  >
>  >  ... and then the metadata is wrong, i.e. does no longer contain all the old releases.
>
>
> True.  The Maven Stage Plugin is meant to help with this:
>  http://maven.apache.org/plugins/maven-stage-plugin/usage.html
>
<snip/>

Ah, I see there is now an alpha release, great.

-Rahul


>  --
>
> Wendy
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]