Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Duplicate
-
None
-
None
-
None
Description
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.