[
https://issues.apache.org/jira/browse/HBASE-8187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13614391#comment-13614391
]
Jesse Yates commented on HBASE-8187:
------------------------------------
Awful may be the nicest way I've heard this described :) Your original argument
wrt to the assembly plugin still holds sway though - as long as we don't update
the version, using assembly:single isn't all that bad. If we ever want to
upgrade the plugin, we would probably need to move to an assembly module, but
until then, the current layout seems fine (+ the fact that plugin dev. seems to
be rather slow makes this not a huge deal to me).
bq. mvn package -Dhadoop.profile=2.0 -Dhadoop.version=2.0.3-alpha
-Dversion=0.95.0-hadoop2
that is just gross. Do we really need the -Dversion=0.95.0-hadoop2 bit? Seems
like all the necessary info is in "Dhadoop.version=2.0.3-alpha" and could be
used to turn on the other profiles
Alternatively, maybe just have a bunch of profiles to use for building (rather
than specifically activated by properties)?
> trunk/0.95 tarball packaging
> ----------------------------
>
> Key: HBASE-8187
> URL: https://issues.apache.org/jira/browse/HBASE-8187
> Project: HBase
> Issue Type: Bug
> Reporter: stack
> Priority: Blocker
>
> Packaging needs work now we have maven multi-moduled. Sounds like folks want
> a package for hadoop1 and hadoop2. Also want source package and maybe even a
> package that includes test jars so can run integration tests.
> Let this be umbrella issue for package fixes. Will hang smaller issues off
> this one as we figure them.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
