dev@jersey.java.net

Maven POM File Issues

From: Greg Logan <greg.logan_at_usask.ca>
Date: Mon, 07 May 2012 16:38:01 -0600

Hi folks,

I'm one of the release managers over at Opencast Matterhorn
(opencastproject.org), and we are hitting a little snag with your POM
files. Older versions of Maven (2.x branch) do not follow the http to
https redirect your repositories are using, and get an exception like
the following when trying to build:

[INFO]
------------------------------------------------------------------------
[INFO] Building matterhorn-ingest-service-impl
[INFO] task-segment: [clean, install]
[INFO]
------------------------------------------------------------------------
[INFO] [clean:clean {execution: default-clean}]
[INFO] Deleting file set:
/home/gdl420/trunk/modules/matterhorn-ingest-service-impl/target
(included: [**], excluded: [])
Downloading:
http://repository.opencastproject.org/nexus/content/groups/public/com/sun/jersey/jersey-server/1.1.5/jersey-server-1.1.5.pom
7K downloaded (jersey-server-1.1.5.pom)
Downloading:
http://maven.glassfish.org/content/groups/glassfish/com/sun/jersey/jersey-project/1.1.5/jersey-project-1.1.5.pom
185b downloaded (jersey-project-1.1.5.pom)
[WARNING] *** CHECKSUM FAILED - Checksum failed on download: local =
'6c9fd3d150b8a5f0ca676f49b8ed603793cabebb'; remote = '<html>
<head><title>301' - RETRYING
Downloading:
http://maven.glassfish.org/content/groups/glassfish/com/sun/jersey/jersey-project/1.1.5/jersey-project-1.1.5.pom
185b downloaded (jersey-project-1.1.5.pom)
[WARNING] *** CHECKSUM FAILED - Checksum failed on download: local =
'6c9fd3d150b8a5f0ca676f49b8ed603793cabebb'; remote = '<html>
<head><title>301' - IGNORING
[1:05:05 PM CST] Greg Logan:
http://repository.opencastproject.org/nexus/content/groups/public/com/sun/jersey/jersey-server/1.1.5/jersey-server-1.1.5.pom

Newer versions of Maven handle the redirect properly, which makes me
think that this is likely a bug of some kind. Unfortunately, Ubuntu
ships with 2.2.1 as the default so we see a lot of people reporting this
issue. Is there any chance you could change your pom files to default
to the https side of things rather than serving up a 301 redirect in
html? I *think* that would solve the issue, although I will admit that
I'm not a Maven expert!

G