hama-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Edward J. Yoon (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HAMA-421) Maven build issues using proxy
Date Wed, 17 Aug 2011 12:42:40 GMT

    [ https://issues.apache.org/jira/browse/HAMA-421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13086273#comment-13086273
] 

Edward J. Yoon commented on HAMA-421:
-------------------------------------

Hama web UI works well with jetty 6.1.14 on my computer. Build also OK.

{code}
11/08/17 21:38:18 INFO http.HttpServer: listener.getLocalPort() returned 40013 webServer.getConnectors()[0].getLocalPort()
returned 40013
11/08/17 21:38:18 INFO http.HttpServer: Jetty bound to port 40013
2011-08-17 21:38:18.183::INFO:  jetty-6.1.14
{code}

BTW, I get the following stacktrace snip from the server and a 500 error shows in any browser.

{code}
java.lang.NoClassDefFoundError: org/apache/tools/ant/BuildListener
        at org.apache.jasper.compiler.Compiler.initJavaCompiler(Compiler.java:716)
        at org.apache.jasper.compiler.Compiler.(Compiler.java:116)
        at org.apache.jasper.JspCompilationContext.createCompiler(JspCompilationContext.java:272)
        at org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:589)
        at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:344)
        at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:470)
        at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:364)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
        at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:487)
        at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:362)
        at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
{code}

I think, we have to add ant dependencies to core pom.xml file.

{code}
      <dependency>
        <groupId>org.apache.ant</groupId>
        <artifactId>ant</artifactId>
        <version>${ant.version}</version>
      </dependency>
      <dependency>
        <groupId>org.apache.ant</groupId>
        <artifactId>ant-launcher</artifactId>
        <version>${ant.version}</version>
      </dependency>
{code}



> Maven build issues using proxy
> ------------------------------
>
>                 Key: HAMA-421
>                 URL: https://issues.apache.org/jira/browse/HAMA-421
>             Project: Hama
>          Issue Type: Bug
>          Components: build 
>            Reporter: Joe Crobak
>            Assignee: Joe Crobak
>         Attachments: HAMA-421.patch
>
>
> We use Artifactory as a maven proxy and it doesn't like some of the pom's that Hama depends
on. In particular:
> # The zookeeper dependency in pom.xml of several services references zookeeper with groupId
org.apache.hadoop. This doesn't match the groupid in the zookeeper-3.3.1.pom, which causes
our proxy to return a 409 with the following in the logs:
> {{The target deployment path 'org/apache/hadoop/zookeeper/3.3.1/zookeeper-3.3.1.pom'
does not match the POM's expected path prefix 'org/apache/zookeeper/zookeeper/3.3.1'. Please
verify your POM content for correctness and make sure the source path is a valid Maven 2 repository
root path.}}
> # The jsp-2.1-6.1.4.pom is malformed -- it has an <includes> nested inside of <includes>
(should be <include> inside <includes>).  This is fixed in jsp-2.1-6.1.12.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message