hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kay Kay (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HBASE-2099) Move build to Maven
Date Fri, 15 Jan 2010 03:00:54 GMT

    [ https://issues.apache.org/jira/browse/HBASE-2099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12800515#action_12800515

Kay Kay commented on HBASE-2099:

but I can't see from the old ivy build system exactly what extra is needed for the 'hbase-core'

 <!--  Test  -->
   <dependency org="org.apache.hadoop" name="hadoop-core-test" 
               rev="${hadoop-core.version}" conf="test->default" transitive="false"/>

   <dependency org="org.apache.hadoop" name="hadoop-hdfs-test" 
               rev="${hadoop-hdfs.version}" conf="test->default" transitive="false"/>

   <dependency org="org.apache.hadoop" name="hadoop-mapred-test" 
               rev="${hadoop-mapred.version}" conf="test->default" transitive="false"/>

   <dependency org="org.apache.commons" name="commons-math" 
               rev="${commons-math.version}" conf="test->default"/> 

These modules are needed for test  configuration, in addition to that of core. 

The error seems to be jetty / jetty-util though . 

Do an 

$ ant compile 

from the cmd line - and look at the list of jars at 

${basedir}/build/lib/ivy/lib/common and compare it with  

$ mvn dependency:copy-dependencies  . 

> 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.3.full.patch,
HBASE-2099.3.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.

View raw message