[
https://issues.apache.org/jira/browse/HBASE-2099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12800381#action_12800381
]
Paul Smith commented on HBASE-2099:
-----------------------------------
bq. "Someone entered an issue for 3.3.0 re maven and source in the jar a while
back, for 3.3.0 we have a patch to the build.xml that will address (4 jars now,
original(current) + bin/src/doc jars for maven repo)"
Ok, good, so they have a plan for that. It's more an annoyance I guess,
there's no functional issue I can think of here, since it's the same source as
the binary, it's just being recompiled (well we HOPE it's the same source
right.. ? :) ). The only trickery here is that if it ISN'T the same source,
then because hbase is lexicographically earlier than zookeeper, in most JVMs I
think it will find the zookeeper classes from the hbase jar, and use those,
basically ignoring the binaries inside zookeeper.
My next steps are in order:
* use the assembly plugin to build the overall tar ball, mimic what ivy does
* make the test cases work (I should work out why they also fail under ivy
first I suspect)
* flesh out the contrib area more (I'm currently only build stargate, and
probably not completely, because I still haven't added the jruby dependency in
just yet for runtime)
I think if I do the first 2, then I'll post more details on the list.
> Move build to Maven
> -------------------
>
> Key: HBASE-2099
> URL: https://issues.apache.org/jira/browse/HBASE-2099
> Project: Hadoop HBase
> Issue Type: Task
> Reporter: stack
> Attachments: HBASE-2099.2.full.patch, HBASE-2099.2.patch,
> HBASE-2099.3.full.patch, HBASE-2099.3.patch, HBASE-2099.patch
>
>
> This issue is for discussing pros and cons of moving hbase build to Apache
> Maven.
> Maven, if you take on its paradigm, does a lot for you. There are also a
> bunch of nice plugins that do nice reports on state of project; findbugs,
> that nice plugin where you can give out urls that will resolve to lines in
> source code (a doxygen-like thing ... I've forgotten its name). Other
> examples are a docbook plugin that would do the build inline with doc build.
> We could start up the hbase book using docbook format and the hbase book
> would ride along with versions.
> As I see it -- and its a while since I've done this stuff so things may have
> since changed -- in the way of an easy move to maven is our src/contrib
> content. Maven would have these as distinct projects pulling in their hbase
> dependency or, if you wanted to take on the maven subproject notion, then,
> hbase would be at same level in build as the contribs -- it would be a
> subproject too just built before the others.
> Anyone interested in working on this issue?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
