hbase-dev mailing list archives

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

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

Paul Smith commented on HBASE-2099:
-----------------------------------

bq. Seems like an artifact of contrib/ec2 reusing build-contrib.xml . See HBASE-2126 , looks
like a build.xml quirk.

Hrm, I don't think that's the problem with the Maven side as yet, I'm getting stuff like:

{noformat}
....
  <testcase time="1.403" classname="org.apache.hadoop.hbase.TestFullLogReconstruction"
name="org.apache.hadoop.hbase.TestFullLogReconstruction">
    <error message="tried to access field org.slf4j.impl.StaticLoggerBinder.SINGLETON from
class org.slf4j.LoggerFactory" type="java.lang.IllegalAccessError">java.lang.IllegalAccessError:
tried to access field org.slf4j.impl.StaticLoggerBinder.SINGLETON from class org.slf4j.LoggerFactory
	at org.slf4j.LoggerFactory.&lt;clinit&gt;(LoggerFactory.java:60)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:597)
	at org.mortbay.log.Slf4jLog.&lt;init&gt;(Slf4jLog.java:64)
	at org.mortbay.log.Slf4jLog.&lt;init&gt;(Slf4jLog.java:37)
...
{noformat}

and

{noformat}
...
  <testcase time="0.18" classname="org.apache.hadoop.hbase.TestZooKeeper" name="org.apache.hadoop.hbase.TestZooKeeper">
    <error message="Could not initialize class org.mortbay.log.Log" type="java.lang.NoClassDefFoundError">java.lang.NoClassDefFoundError:
Could not initialize class org.mortbay.log.Log
	at org.mortbay.component.Container.add(Container.java:200)
	at org.mortbay.component.Container.update(Container.java:164)
	at org.mortbay.component.Container.update(Container.java:106)
	at org.mortbay.jetty.Server.setConnectors(Server.java:158)
	at org.mortbay.jetty.Server.addConnector(Server.java:132)
	at org.apache.hadoop.http.HttpServer.&lt;init&gt;(HttpServer.java:119)
	at org.apache.hadoop.hdfs.server.namenode.NameNode.startHttpServer(NameNode.java:344
...
{noformat}

I suspect there are more dependencies needed to be brought in for testing, but I can't see
from the old ivy build system exactly what extra is needed for the 'hbase-core' tests (nothing
to do with hbase-contrib as yet).

But I haven't spent much time on that yet, but if anyone can spot the problem, feel free to
let me know...

> 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.


Mime
View raw message