[
https://issues.apache.org/jira/browse/HCATALOG-601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13565759#comment-13565759
]
Sushanth Sowmyan edited comment on HCATALOG-601 at 1/29/13 8:24 PM:
--------------------------------------------------------------------
~traviscrawford : To be honest, if it's in another pom.xml as with jersey-1.9,
then no, it doesn't help. It only serves as documentation then, and I added it
mostly to be consistent with our other entry for glassfish.
It looks like this is brought in as a dep from grizzly-project-2.1.1, which
itself is brought in as a dep from jersey-1.8 (wow!) which is brought in by
hadoop-common, so I guess this comes up only when compiling with
mvn.hadoop.profile=hadoop23 ? I'm pretty sure I had this happen before I was
testing with hadoop23, but not able to reproduce it now.
was (Author: sushanth):
~Travis : To be honest, if it's in another pom.xml as with jersey-1.9, then
no, it doesn't help. It only serves as documentation then, and I added it
mostly to be consistent with our other entry for glassfish.
It looks like this is brought in as a dep from grizzly-project-2.1.1, which
itself is brought in as a dep from jersey-1.8 (wow!) which is brought in by
hadoop-common, so I guess this comes up only when compiling with
mvn.hadoop.profile=hadoop23 ? I'm pretty sure I had this happen before I was
testing with hadoop23, but not able to reproduce it now.
> 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
