Travis Crawford created HCATALOG-601:
----------------------------------------
Summary: 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
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
