You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@maven.apache.org by ws...@apache.org on 2008/02/18 20:15:28 UTC

svn commit: r628845 - /maven/pom/trunk/maven/pom.xml

Author: wsmoak
Date: Mon Feb 18 11:15:26 2008
New Revision: 628845

URL: http://svn.apache.org/viewvc?rev=628845&view=rev
Log:
Override the distribution url to avoid inaadvertently publishing directly to the rsynced repo.

Modified:
    maven/pom/trunk/maven/pom.xml

Modified: maven/pom/trunk/maven/pom.xml
URL: http://svn.apache.org/viewvc/maven/pom/trunk/maven/pom.xml?rev=628845&r1=628844&r2=628845&view=diff
==============================================================================
--- maven/pom/trunk/maven/pom.xml (original)
+++ maven/pom/trunk/maven/pom.xml Mon Feb 18 11:15:26 2008
@@ -82,6 +82,10 @@
   </mailingLists>
 
   <distributionManagement>
+    <repository>
+      <id>maven.staging</id>
+      <url>scp://people.apache.org/www/people.apache.org/builds/maven/${project.version}/staging-repo</url>
+    </repository>
     <site>
       <id>apache.website</id>
       <url>scp://people.apache.org/www/maven.apache.org</url>



Re: svn commit: r628845 - /maven/pom/trunk/maven/pom.xml

Posted by Dennis Lundberg <de...@apache.org>.
Wendy Smoak wrote:
> On Feb 18, 2008 4:12 PM, Dennis Lundberg <de...@apache.org> wrote:
>> Hi Wendy
>>
>> Did you mean for this to go into Maven parent pom?
>>
>> The URL in your change suggests to me that is intended for Maven
>> components pom. If left in Maven parent pom there will be URL clashes
>> between say Maven 2.1 and Maven Project Info reports Plugin 2.1
> 
> I don't expect it to actually be used.  Our release instructions say
> to define a deploy.altRepository property in settings.xml, and (at
> least for plugins) the release plugin is configured to use that.
> 
> I want it in the parent pom to prevent any inadvertent publishing
> directly to m2-ibiblio-rsync-repository (which should never be
> published to directly, all releases should be staged for review.)  And
> if it does somehow get used, the version number will keep _most_
> things separate.
> 
> If a sub-project does want a shared staging area, it can override this
> in the top-level pom for that sub-project.  Archiva does it this way,
> see http://people.apache.org/builds/maven/archiva/ (which we need to
> clean up!)

Thanks for the explanation. That sounds like a worthwhile addition.

-- 
Dennis Lundberg

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


Re: svn commit: r628845 - /maven/pom/trunk/maven/pom.xml

Posted by Wendy Smoak <ws...@gmail.com>.
On Feb 18, 2008 4:12 PM, Dennis Lundberg <de...@apache.org> wrote:
> Hi Wendy
>
> Did you mean for this to go into Maven parent pom?
>
> The URL in your change suggests to me that is intended for Maven
> components pom. If left in Maven parent pom there will be URL clashes
> between say Maven 2.1 and Maven Project Info reports Plugin 2.1

I don't expect it to actually be used.  Our release instructions say
to define a deploy.altRepository property in settings.xml, and (at
least for plugins) the release plugin is configured to use that.

I want it in the parent pom to prevent any inadvertent publishing
directly to m2-ibiblio-rsync-repository (which should never be
published to directly, all releases should be staged for review.)  And
if it does somehow get used, the version number will keep _most_
things separate.

If a sub-project does want a shared staging area, it can override this
in the top-level pom for that sub-project.  Archiva does it this way,
see http://people.apache.org/builds/maven/archiva/ (which we need to
clean up!)

-- 
Wendy

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


Re: svn commit: r628845 - /maven/pom/trunk/maven/pom.xml

Posted by Dennis Lundberg <de...@apache.org>.
Hi Wendy

Did you mean for this to go into Maven parent pom?

The URL in your change suggests to me that is intended for Maven 
components pom. If left in Maven parent pom there will be URL clashes 
between say Maven 2.1 and Maven Project Info reports Plugin 2.1

wsmoak@apache.org wrote:
> Author: wsmoak
> Date: Mon Feb 18 11:15:26 2008
> New Revision: 628845
> 
> URL: http://svn.apache.org/viewvc?rev=628845&view=rev
> Log:
> Override the distribution url to avoid inaadvertently publishing directly to the rsynced repo.
> 
> Modified:
>     maven/pom/trunk/maven/pom.xml
> 
> Modified: maven/pom/trunk/maven/pom.xml
> URL: http://svn.apache.org/viewvc/maven/pom/trunk/maven/pom.xml?rev=628845&r1=628844&r2=628845&view=diff
> ==============================================================================
> --- maven/pom/trunk/maven/pom.xml (original)
> +++ maven/pom/trunk/maven/pom.xml Mon Feb 18 11:15:26 2008
> @@ -82,6 +82,10 @@
>    </mailingLists>
>  
>    <distributionManagement>
> +    <repository>
> +      <id>maven.staging</id>
> +      <url>scp://people.apache.org/www/people.apache.org/builds/maven/${project.version}/staging-repo</url>
> +    </repository>
>      <site>
>        <id>apache.website</id>
>        <url>scp://people.apache.org/www/maven.apache.org</url>
> 
> 
> 


-- 
Dennis Lundberg

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