incubator-hama-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joe Crobak (JIRA)" <>
Subject [jira] [Commented] (HAMA-421) Maven build issues using proxy
Date Wed, 17 Aug 2011 11:42:27 GMT


Joe Crobak commented on HAMA-421:

bq. This patches hard-codes the version of jetty to 6.1.12 in one place (around line 138).
It would probably be better to update ${jetty.version} in the <properties/> section,

I wasn't sure if there was a particular reason that hama depends on the older version of jetty.
 If it's ok to upgrade, then it would probably make sense to switch to either jetty 6.1.14
(which hadoop-0.20.2 depends on) or to jetty 6.1.26 (the latest in the jetty 6.1.x line).
Any thoughts on which makes the most sense?

> Maven build issues using proxy
> ------------------------------
>                 Key: HAMA-421
>                 URL:
>             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:


View raw message