You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@struts.apache.org by Wendy Smoak <ws...@gmail.com> on 2006/12/13 05:03:06 UTC

Maven build & release changes

The new struts-master pom has the following distribution management section:

   <distributionManagement>
      <repository>
         <id>struts-staging</id>
         <name>Apache Struts Staging Repository</name>
         <url>scp://people.apache.org/www/people.apache.org/builds/struts/m2-staging-repository</url>
      </repository>
       ...

This means that if the version number does not end in -SNAPSHOT, the
artifacts will be deployed to
http://people.apache.org/builds/struts/m2-staging-repository.

(Previously, we were staging releases in the snapshot repository.)

I've updated both 'how to build' wiki pages with a new profile to put
in your settings.xml file:

      <profile>
         <id>struts-staging</id>
         <repositories>
            <repository>
               <id>struts-staging</id>
               <url>http://people.apache.org/builds/struts/m2-staging-repository</url>
               <snapshots><enabled>false</enabled></snapshots>
               <releases><enabled>true</enabled></releases>
            </repository>
         </repositories>
      </profile>

If you need Maven to download artifacts from the staging repository,
use -Pstruts-staging on the command line to enable this profile.  This
isn't something you'd want to have enabled all the time.

Both s1 and s2 are pointed at the same staging repo, so we'll have to
coordinate releases or switch to a different place for one of them.
Somehow I don't think it will be a problem...

Over in Maven-land things are moving closer to having release staging
and acceptance/promotion as part of the standard Maven release
process.

-- 
Wendy

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