[
https://issues.apache.org/jira/browse/HBASE-11832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14126783#comment-14126783
]
Hudson commented on HBASE-11832:
--------------------------------
SUCCESS: Integrated in HBase-1.0 #164 (See
[https://builds.apache.org/job/HBase-1.0/164/])
HBASE-11832 maven release plugin overrides command line arguments (Enoch Hsu)
(enis: rev 32a8bb44a3d7e360c14d032d2dc0b396aa2c3582)
* pom.xml
> maven release plugin overrides command line arguments
> -----------------------------------------------------
>
> Key: HBASE-11832
> URL: https://issues.apache.org/jira/browse/HBASE-11832
> Project: HBase
> Issue Type: Bug
> Affects Versions: 0.98.4
> Reporter: Enoch Hsu
> Assignee: Enoch Hsu
> Priority: Minor
> Fix For: 0.99.0, 2.0.0
>
> Attachments: HBASE-11832.patch
>
>
> Inside the pom under the maven-release-plugin there is a configuration that
> defines what the release-plugin uses like so
> <configuration>
> <!--You need this profile. It'll sign your artifacts.
> I'm not sure if this config. actually works though.
> I've been specifying -Papache-release on the command-line
> -->
> <releaseProfiles>apache-release</releaseProfiles>
> <!--This stops our running tests for each stage of maven release.
> But it builds the test jar. From SUREFIRE-172.
> -->
> <arguments>-Dmaven.test.skip.exec</arguments>
> <pomFileName>pom.xml</pomFileName>
> </configuration>
> The arguments are hardcoded in and will automatically override any arguments
> the user passes in from the command line.
> I propose to modify this to the following
> <arguments>-Dmaven.test.skip.exec ${arguments}</arguments>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
