[
https://issues.apache.org/jira/browse/HBASE-10790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13941443#comment-13941443
]
stack commented on HBASE-10790:
-------------------------------
In hadoop, there is a dist profile and then you have to add a -Dtar to actually
get a tar ball. It is a different kind of cryptic to what we have now in
hbase. In hbase, our philosophy is you must call out what you want; i.e. you
say if you want the docs and if you want an assembly. We arrived here because
hooking up doc building or assembly as by-products of standard maven goals
makes simple checks like whether your change compiles excruciating as you must
wait on javadoc, etc (see Enis comment above). And then some tasks do not fit
mvn standard model when it a multi-module project as hbase is; for example the
javadoc aggregate goal which seemingly must be called out as explicit goal or
even the assembly if you want to include site/doc.
Is it that you just forget to add the assembly:single or is it that you think
the tar ball should always be produced [~liushaohui]? How much longer does it
take to make the tarball? If you include tarball as goal in package, can we
still include site and doc? Thanks.
> make assembly:single as default in pom.xml
> ------------------------------------------
>
> Key: HBASE-10790
> URL: https://issues.apache.org/jira/browse/HBASE-10790
> Project: HBase
> Issue Type: Improvement
> Reporter: Liu Shaohui
> Assignee: Liu Shaohui
> Priority: Minor
> Attachments: HBASE-10790-trunk-v1.diff
>
>
> Now to compile a HBase tar release package, we should use
> the cmd:
> {code}
> mvn clean package assembly:single
> {code}, which is not convenient. We can make assembly:single as a default
> option and run the assembly plugin in maven package phase. Then we can just
> use the cmd {code} mvn clean package {code} to get a release package.
> Other suggestions are welcomed.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
