[
https://issues.apache.org/jira/browse/HBASE-2099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12799577#action_12799577
]
Paul Smith commented on HBASE-2099:
-----------------------------------
bq. That the generated jar, hbase-0.21.0-dev.jar, has a hbase-default.xml in
top-level and in a conf subdir looks wrong. I think the top-level one is the
one we want. Whatever, its not your prob. Just make an issue on it and one of
us will figure it.
ok, that's fine, I figured it was the top-level one, I'll just make it only do
that one
bq. Its finding java files in the zk jar and compiling them?
yep, it appears to 'find' these as part of it's java source location mechanism.
It's odd that the zookeeper binary artifact has the .java files embedded with
it (go check, it's there), but Maven shouldn't really be doing that if it's not
within the defined compilation directories.
bq. On moving dirs, thats no problem (Can't make an omelette...)
Mine might be a spicy omelette, is someone ok to handle any ivy changes as we
make progress?
> 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.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.
