[
https://issues.apache.org/jira/browse/HBASE-13598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Purtell reopened HBASE-13598:
------------------------------------
bq. "attach the created assembly to the project so that it will be uploaded
into the repository on the install and deploy goals"
Whoa. So does this mean that when we do mvn deploy during a release now the
tarballs will be pushed up to Maven? We don't want that, right?
> Make hbase assembly 'attach' to the project
> -------------------------------------------
>
> Key: HBASE-13598
> URL: https://issues.apache.org/jira/browse/HBASE-13598
> Project: HBase
> Issue Type: Improvement
> Reporter: Jerry He
> Assignee: Jerry He
> Priority: Minor
> Fix For: 2.0.0, 1.2.0
>
> Attachments: HBASE-13598-master.patch
>
>
> Currently for hbase assembly, we set 'attach' to 'false':
> hbase-assembly/pom.xml:
> {code}
> <!--We do not want assembly attached; run on command-line explicitly
> - if you want to do an assembly-->
> - <attach>false</attach>
> {code}
> The result is that the hbase assembly tarball will not be deployed via 'mvn
> install' or 'maven deploy'
> There are Apache projects that directly uses the hbase assembly tarball in
> their build process. For example, Slider HBase package and Ambari 2.0
> Metrics.
> Here is the link the maven assembly plug info on the 'attach':
> https://maven.apache.org/plugins/maven-assembly-plugin/single-mojo.html#attach
> {code}
> attach:
> Controls whether the assembly plugin tries to attach the resulting assembly
> to the project.
> Type: boolean
> Since: 2.2-beta-1
> Required: No
> User Property: assembly.attach
> Default: true
> {code}
> The assembly will only be built if 'assembly:single' is specified, and then
> deployed in 'maven install' or 'maven deploy'
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
