[
https://issues.apache.org/jira/browse/HBASE-12121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-12121:
--------------------------
Resolution: Fixed
Fix Version/s: 0.98.10
Hadoop Flags: Reviewed
Status: Resolved (was: Patch Available)
Pushed to 0.98+
> maven release plugin does not allow for customized goals
> --------------------------------------------------------
>
> Key: HBASE-12121
> URL: https://issues.apache.org/jira/browse/HBASE-12121
> Project: HBase
> Issue Type: Improvement
> Components: build
> Affects Versions: 0.98.6
> Reporter: Enoch Hsu
> Assignee: Enoch Hsu
> Priority: Minor
> Fix For: 1.0.0, 2.0.0, 0.98.10
>
> Attachments: HBASE-12121.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>
> There is no property for goals so if the user passes in a goal from the
> command line it will not get executed and the default behavior will be used
> instead.
> I propose to add in the following
> <goals>${goals}</goals>
> This will allow custom release goal options
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
