You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hama.apache.org by "Edward J. Yoon (JIRA)" <ji...@apache.org> on 2011/08/17 01:03:27 UTC
[jira] [Assigned] (HAMA-421) Maven build issues using proxy
[ https://issues.apache.org/jira/browse/HAMA-421?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Edward J. Yoon reassigned HAMA-421:
-----------------------------------
Assignee: Joe Crobak
> 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