You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Steve Loughran (JIRA)" <ji...@apache.org> on 2014/10/27 12:18:34 UTC
[jira] [Commented] (HADOOP-11232) jersey-core-1.9 has a faulty
glassfish-repo setting
[ https://issues.apache.org/jira/browse/HADOOP-11232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14185069#comment-14185069 ]
Steve Loughran commented on HADOOP-11232:
-----------------------------------------
Probably the remote repo going down triggered this. Updating any nexus POM is dangerous as it now makes for even more inconsistent build results.
Another fix should be for hadoop-common to explicitly include the artifacts that jersey 1.9 asks for -at which point there is no need for maven to follow up the transitive query.
> jersey-core-1.9 has a faulty glassfish-repo setting
> ---------------------------------------------------
>
> Key: HADOOP-11232
> URL: https://issues.apache.org/jira/browse/HADOOP-11232
> Project: Hadoop Common
> Issue Type: Bug
> Components: build
> Reporter: Tsz Wo Nicholas Sze
> Assignee: Sushanth Sowmyan
>
> The following was reported by [~sushanth].
> hadoop-common brings in jersey-core-1.9 as a dependency by default.
> This is problematic, since the pom file for jersey 1.9 hardcode-specifies glassfish-repo as the place to get further transitive dependencies, which leads to a site that serves a static "this has moved" page instead of a 404. This results in faulty parent resolutions, which when asked for a pom file, get erroneous results.
> The only way around this seems to be to add a series of exclusions for jersey-core, jersey-json, jersey-server and a bunch of others to hadoop-common, then to hadoop-hdfs, then to hadoop-mapreduce-client-core. I don't know how many more excludes are necessary before I can get this to work.
> If you update your jersey.version to 1.14, this faulty pom goes away. Please either update that, or work with build infra to update our nexus pom for jersey-1.9 so that it does not include the faulty glassfish repo.
> Another interesting note about this is that something changed yesterday evening to cause this break in behaviour. We have not had this particular problem in about 9+ months.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)