[HCATALOG-601] fix hcatalog dependency resolution issues

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.5
• Component/s: build
• Assignee: Sushanth Sowmyan
• Reporter: Travis Crawford
• Created: 18/Jan/13 18:09
• Updated: 15/Feb/13 21:32
• Resolved: 30/Jan/13 22:04

Description

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:

<repository>
  <id>glassfish-repository</id>
  <name>Repository for Glassfish</name>
  <url>
    http://maven.glassfish.org/content/groups/glassfish
  </url>
</repository>

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.