[
https://issues.apache.org/jira/browse/HBASE-2099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12799590#action_12799590
]
Paul Smith commented on HBASE-2099:
-----------------------------------
I can't think of a seamless way of doing it that doesn't involve either keeping
Ivy configs in sync, or having a bit of flexibility (ie. downtime) while the
reshuffling is is done.
What I can probably do is do exactly what I did for our corporate mavenization.
I took a branch off trunk, and built a sequence of steps to make the Maven
switch, with a good bit of testing (lots of jar diffs).
Once complete, we held off commits to trunk for a short while while the
migration script was applied (in my case I did it manually, step by step, was
only about a dozen or so commands), then commit.
So perhaps we can do that, have a working test branch that someone can follow
my steps locally for review and then once you guys are happy, you could run
these steps yourself on trunk.
i don't know how much work keeping ivy in sync would be, risking some
brittleness in trunk. How many dev build trunk ? I'm not sure how big the
hbase-dev team is, if it's small, that maybe ok, but if it's big it could be a
bit of an inconvenience.
> 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.
