Hi,
I can confirm that I'm having the same issues as Stephen when releasing
but didn't took the time to figure out the cause: I knew the workaround
and thought it had to do with my settings.xml.
The issue of the m-release-p for not picking up the profile was fixed in
MRELEASE-459 [1], together with a lot of other profile related issues.
However, we're still struggling with GIT (SCM-709), so for the apache-pom
we should either stay on m-release-p 2.3.2 or m-release-p 2.4.2 with
scm-1.7 (if possible)
Robert
[1] https://jira.codehaus.org/browse/MRELEASE-459
Op Wed, 13 Nov 2013 17:50:02 +0100 schreef Benson Margulies
<[email protected]>:
On Wed, Nov 13, 2013 at 11:33 AM, Stephen Connolly
<[email protected]> wrote:
The profiles are not being activated... this is why in the asf pom we
use
the -P... in the <arguments> tag
Why aren't the profiles activated? Does 'arguments' disable
'releaseProfiles'?
On 13 November 2013 16:01, Benson Margulies <[email protected]>
wrote:
On Wed, Nov 13, 2013 at 10:54 AM, Stephen Connolly
<[email protected]> wrote:
> On 27 October 2012 22:00, <[email protected]> wrote:
>
>> Author: bimargulies
>> Date: Sat Oct 27 21:00:24 2012
>> New Revision: 1402867
>>
>> URL: http://svn.apache.org/viewvc?rev=1402867&view=rev
>> Log:
>> MPOM-38: Enable RAT to help us get maven releases to be
license-header
>> compliant
>> o Also configure the release plugin to turn on rat (quietly)
>>
>> 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=1402867&r1=1402866&r2=1402867&view=diff
>>
>>
==============================================================================
>> --- maven/pom/trunk/maven/pom.xml (original)
>> +++ maven/pom/trunk/maven/pom.xml Sat Oct 27 21:00:24 2012
>> @@ -806,12 +806,43 @@ under the License.
>> <artifactId>findbugs-maven-plugin</artifactId>
>> <version>2.5.2</version>
>> </plugin>
>> + <plugin>
>> + <groupId>org.apache.maven.plugins</groupId>
>> + <artifactId>maven-release-plugin</artifactId>
>> + <version>2.3.2</version>
>> + <configuration>
>> + <useReleaseProfile>true</useReleaseProfile>
>> + <releaseProfiles>apache-release,rat</releaseProfiles>
>> + <goals>deploy</goals>
>> + <arguments>${arguments}</arguments>
>>
>
> FYI This just blew up in my face with Doxia 1.5. I had to resort to
> re-running release:perform with -DconnectupUrl=...
> -Darguments=-P+apache-release,rat to get the release to stage
correctly
> with GPG signature etc...
What's special about doxia, or, alternatively, what's wrong here?
>
>
>> + </configuration>
>> + </plugin>
>> </plugins>
>> </pluginManagement>
>> </build>
>>
>> <profiles>
>> <profile>
>> + <id>rat</id>
>> + <build>
>> + <plugins>
>> + <plugin>
>> + <groupId>org.apache.rat</groupId>
>> + <artifactId>apache-rat-plugin</artifactId>
>> + <executions>
>> + <execution>
>> + <phase>verify</phase>
>> + <goals>
>> + <!-- rat, not check, because we've got lots of
>> noncomplaint stuff -->
>> + <goal>rat</goal>
>> + </goals>
>> + </execution>
>> + </executions>
>> + </plugin>
>> + </plugins>
>> + </build>
>> + </profile>
>> + <profile>
>> <id>quality-checks</id>
>> <activation>
>> <property>
>>
>>
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
