[
https://issues.apache.org/jira/browse/HBASE-8187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13617146#comment-13617146
]
stack commented on HBASE-8187:
------------------------------
[~enis] Book in assembly is weird? Its kinda weird being up top level too? I
could put it back?
I can't make the -Dversion=hbase-0.97.0-hadoop2 work. I tried a few things
defining -Dpom.version or setting the property to be non-maven as in
-Dhbase.version= ... but having property for version messes up the assembly;
nothing gets copied over into the lib dir (but for three *-test.jars that we
are hand-copying). Not sure what is going on here. I tried the following but
mvn didn't like it either:
{code}
[WARNING]
[WARNING] Some problems were encountered while building the effective model for
org.apache.hbase:hbase:pom:0.97.0-hadoop${hadoop.profile}-SNAPSHOT
[WARNING] 'version' contains an expression but should be a constant. @ line 42,
column 12
[WARNING]
{code}
We might have to "branch" to make the hadoop2 artifacts so we can replace
0.97.0-SNAPSHOT with 0.97.0-hadoop2-SNAPSHOT everywhere its hardcoded in poms
as pom.version... not the end of the world.
Let me put up new patch. I can now make a rough 'src'/'project' layout w/ this
command:
MAVEN_OPTS="-Xmx3g" mvn install -DskipTests -DdescriptorId=project
-Dassembly.file="src/assembly/src.xml" assembly:single
Next up is trying to publish snapshot to mvn repo.
> 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
> Attachments: 8187.txt
>
>
> 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
