[ 
https://issues.apache.org/jira/browse/HBASE-8187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13613514#comment-13613514
 ] 

stack commented on HBASE-8187:
------------------------------

This is useless:

{code}
MAVEN_OPTS="-Xmx3g" mvn clean install -DskipTests -DdescriptorId=src 
assembly:assembly
{code}

... as is this:

{code}
MAVEN_OPTS="-Xmx3g" mvn clean install -DskipTests -DdescriptorId=src 
assembly:assembly
{code}

Makes near empty assemblies; doesn't factor in the multi-modules (the src does 
include the top-level modules src).

I'm now back to messing w/ assemblies.

Enis reminded of need to be able to produce an artifact that includes/runs-on 
hadoop2:

"Can we do it the current way of the
hadoop.profile + the version specified by the command line. I was thinking
like a BUILDING.txt including
To build the release from the source, use:

mvn package -Dhadoop.profile=2.0 -Dhadoop.version=2.0.3-alpha
-Dversion=0.95.0-hadoop2"
                
> 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

Reply via email to