[
https://issues.apache.org/jira/browse/HBASE-2099?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul Smith updated HBASE-2099:
------------------------------
Attachment: HBASE-2099.2.full.patch
HBASE-2099.2.patch
Latest version of the 'patch'. I've included 2 forms, a full, and a 'lite'
version that contains only the pom files (makes it easier to review).
At this stage, the major surgery includes only:
# creation of a new core directory (plus pom, with external references)
# relocating src/contrib to be a top-level tree.
I now move on to larger scale svn mv hackery, I'm not 100% sure how this will
come out in svn diff form, I may have to just produce a document with all the
commands necessary to accomplish it (I had found in a previous large scale
maven migration that doing an svn mv, but with people checking in new and
modified files into the old directory BEFORE the mv is committed ensures major
headaches under svn).
I hadn't thought of the JDK vs JRE point of view before. There's a
maven-jspc-plugin, so we should be able to accomplish the same thing here no
problems.
> 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.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.
