[
https://issues.apache.org/jira/browse/HBASE-2099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12830591#action_12830591
]
Kay Kay commented on HBASE-2099:
--------------------------------
{quote}
.bq I generated the ant/ivy generated binary with the latest trunk for
comparison, oddly it currently dosen't include sources, or test jars. Maybe
that's a fallout of the ivy transition?
Yes. I believe so. Ivy tarball needs a bit of attention.
{quote}
Paul / stack - Yes , the 'tar' target had an issue after ivy transition, about
how we want to pack the lib in the final distribution. HBASE-2128 tracks it.
I believe we did not have a consensus then about how to pack independent jars
of core and contrib into the lib directory.
The final that I submitted puts together everything under ./lib directory for a
release.
> 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: findbugs.html, findbugs.html, HBase Move Script.txt,
> HBASE-2099.9.patch, test-reports.zip
>
>
> 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.
