[
https://issues.apache.org/jira/browse/HCATALOG-601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13565691#comment-13565691
]
Chris Drome commented on HCATALOG-601:
--------------------------------------
[~traviscrawford] Mithun and I ran into this problem when in the course of
investigating our broken CI builds.
It is largely as [~sushanth] mentions in some of his comments above.
We found that problem starts with jersey-core-1.9.1 which defines
jersey-project-1.9.1 as its parent. The problem is in this pom file as it
defines jvnet-parent as its parent and defines a set of repositories which
include the glassfish repository
(http://maven.glassfish.org/content/groups/glassfish). This is currently
returning a 404.
Here is where the problem occurs, as
http://maven.glassfish.org/content/groups/public will redirect to
https://maven.java.net/content/groups/public from which you can successfully
download the jvnet-parent.
As a temporary work around until the repositories can be fixed, we have patched
the jersey-project-1.9.1.pom to include the correct repository path, and
pre-populate the .m2 cache with this correct pom file.
As was mentioned above, we tried disabling the glassfish repository in favor of
the correct location. However, it appears that the hard-coded values in
jersey-project-1.9.1.pom override any other directives that we tried.
> fix hcatalog dependency resolution issues
> -----------------------------------------
>
> Key: HCATALOG-601
> URL: https://issues.apache.org/jira/browse/HCATALOG-601
> Project: HCatalog
> Issue Type: Bug
> Components: build
> Reporter: Travis Crawford
> Assignee: Travis Crawford
> Fix For: 0.5
>
> Attachments: HCATALOG-601.1.patch, HCATALOG-601.2.patch,
> HCATALOG-601.3.patch
>
>
> Currently HCatalog dependency resolution fails when starting with an empty
> cache. This often manifests itself as the build failing when trying to unzip
> a jar, but the file is actually an HTML error page stored in the local maven
> cache.
> I *think* this is because of our jersey dependency. Currently we depend on
> jersey 1.9.1, which contains the following in
> [jersey-project-1.9.1.pom|http://search.maven.org/remotecontent?filepath=com/sun/jersey/jersey-project/1.9.1/jersey-project-1.9.1.pom]:
> {code}
> <repository>
> <id>glassfish-repository</id>
> <name>Repository for Glassfish</name>
> <url>
> http://maven.glassfish.org/content/groups/glassfish
> </url>
> </repository>
> {code}
> However, visiting that URL gives you a 404 as its no longer a maven repo. I
> believe this transitive repo is getting pulled into our build and causing
> havoc. Looking in our root-level pom we attempt to disable it, but that does
> not appear to be effective.
> Starting in jersey 1.10 the glassfish repo was removed. I believe by bumping
> our jsersey version we can resolve this issue. There was a minor packaging
> change (we now need {{jersey-servlet}} but otherwise its a minor (local - not
> sure about jersey) change.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
