[
https://issues.apache.org/jira/browse/HBASE-2099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12840358#action_12840358
]
Lars Francke commented on HBASE-2099:
-------------------------------------
I really don't want to start a discussion about Maven vs. Ant. I just like the
Maven style better. It is true that there is a lot of incorrect meta data and
we're in the process of weeding out those dependencies that are really needed.
If you use Ant the process is bottom up. You start with nothing and have to
figure out what you need. I'd say it depends on what you prefer.
1. I don't think that's necessary or even a good idea. As you said: Artifacts
aren't allowed to change (at least in the central repository) so there is
really no need to clean the local repository; it just makes the builds take
longer.
2. Can't say a lot about that except that the Wagon and Cargo plugins make it
pretty easy to deploy and run stuff on other machines. But I'm still not sure I
can follow you - I haven't yet done any very complex deployment operations
(just deployment to a remote Tomcat etc. with Cargo) with Maven but if it can
be done with Ant it can be done with Maven ;-) Either way: Maven now seems to
do everything we need for HBase but Ant and Ivy worked too.
As to the clean up: The unit tests currently build their stuff in a "build" or
"data" directoy. When we abort a build for whatever reasons those might not be
cleaned up and they won't be picked up by the clean plugin. This is something
I'll have to remember to look at.
> 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.13.patch, HBASE-2099.14.patch, mvn.out, 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.
