[all] parent pom repositories

[Torsten Curdt]

As we talked about on how to do release on at commons I am wondering  
if these profiles really make sense:

      <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>
        </repository>
      </distributionManagement>
      <id>rc</id>
      <distributionManagement>
        <repository>
          <id>apache.snapshots</id>
          <name>Apache Development Snapshot Repository</name>
          <url>${commons.deployment.protocol}://people.apache.org/ 
www/people.apache.org/repo/m2-snapshot-repository</url>
        </repository>
        <snapshotRepository>
          <id>apache.snapshots</id>
          <name>Apache Development Snapshot Repository</name>
          <url>${commons.deployment.protocol}://people.apache.org/ 
www/people.apache.org/repo/m2-snapshot-repository</url>
        </snapshotRepository>
      </distributionManagement>

I think we agreed that the RCs should have the final version numbers  
in the POM. And that actually doing a release should rather be moving  
the artifacts from one directory to the other than re-building them  
and have maven publish them on the rsync repository. So I am  
wondering whether something like this would make more sense in the  
parent POM:

         <id>rc</id>
         <repositories>
            <repository>
               <id>rc</id>
               <url>http://people.apache.org/builds/commons</url>
               <snapshots><enabled>false</enabled></snapshots>
               <releases><enabled>true</enabled></releases>
            </repository>
         </repositories>

So we would basically always do a

 export PASSPHRASE=secret
 mvn release:prepare -Prc
 mvn release:perform -Prc -Dgpg.passphrase=$PASSPHRASE -Darguments="- 
Prc -Dgpg.passphrase=$PASSPHRASE"

then do the vote and when it comes through just move the atifacts on  
the disk. (Actually we could have a plugin do that for us as well)

Question is what do we do about the conventional artifacts (build  
from the assembly plugin). Doing the signing etc by hand is  
cumbersome if the above already does everything via maven. We need  
less work - not more.

WDYT?

cheers
--
Torsten


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]