commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Antonio Petrelli <antonio.petre...@gmail.com>
Subject Re: [infra] Digester 2.1 release blocked Was [Digester] Auth fail when copying artifacts from staging
Date Fri, 24 Sep 2010 08:36:42 GMT
2010/9/24 Simone Tripodi <simone.tripodi@gmail.com>:
> thanks a lot for your help!!! During the final phase of release I
> wasn't using profiles at all

You didn't, but unfortunately I discovered that commons-parent does. I
see this in commons-parent pom:

<plugin>
            <artifactId>maven-release-plugin</artifactId>
            <configuration>
              <!-- Pass these arguments to the deploy plugin. -->
              <arguments>-Prc</arguments>
            </configuration>
          </plugin>

This overrides the configuration in org.apache:apache:7

<plugin>
          <groupId>org.apache.maven.plugins</groupId>
          <artifactId>maven-release-plugin</artifactId>
          <version>2.0-beta-9</version>
          <configuration>
            <useReleaseProfile>false</useReleaseProfile>
            <goals>deploy</goals>
            <arguments>-Papache-release</arguments>
          </configuration>
        </plugin>

IOW, the "rc" profile is activated instead of "apache-release" and it
deploys in people.a.o. I suggest to contact the commons-parent
maintainer to fix this and, as a temporary fix, run:
mvn release:perform -Darguments="-Papache-release"
Or try to modify the "release.properties" file (generated after you
ran release:prepare) to do this exact thing.
It should work this way.

Ciao
Antonio

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


Mime
View raw message