maven build failed for glassfish dependency

Question

I'm getting the following error consistently on a Maven build. I can't figure out what's happening. What's the technical explanation?

Downloading: http://maven.glassfish.org/content/groups/glassfish/com/sun/jersey/jersey-project/1.2/jersey-project-1.2.pom
185b downloaded  (jersey-project-1.2.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.2/jersey-project-1.2.pom
185b downloaded  (jersey-project-1.2.pom)
[WARNING] *** CHECKSUM FAILED - Checksum failed on download: local = '6c9fd3d150b8a5f0ca676f49b8ed603793cabebb'; remote = '<html>
<head><title>301' - IGNORING
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Error building POM (may not be this project's POM).


Project ID: null:jersey-server:bundle:null

Reason: Cannot find parent: com.sun.jersey:jersey-project for project: null:jersey-server:bundle:null for project null:jersey-server:bundle:null


[INFO] ------------------------------------------------------------------------
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Unable to get dependency information: Unable to read the metadata file for artifact 'com.sun.jersey:jersey-server:jar': Cannot find parent: com.sun.jersey:jersey-project for project: null:jersey-server:bundle:null for project null:jersey-server:bundle:null
  com.sun.jersey:jersey-server:jar:1.2

Maybe you could show us your `pom.xml` and make it easier for us to find out what's wrong? — maba, Jun 12 '12 at 06:57
You must give us your `pom.xml` and the repository settings from your `settings.xml`. — Oliver, Jun 13 '12 at 06:23

score 0 · Answer 1 · answered Jun 27 '12 at 09:39

i met the same problem ,in fact ,the glassfish repository has been 301. so if we can use the central reposity first,there won't be these problems. NOW my method is to modify the pom file which use the glassfish repository . Delete some lines about the repository. Then it can work this time. BUT soon another problem com ,So many pom contains the glassfish. And i modify the next. OH, too many.

score 0 · Answer 2 · answered Oct 20 '12 at 06:32

Please check your jersey-project pom file in you local repository
~/m2/repository/com/sun/jersey/jersey-project/1.2/jersey-project-1.2.pom C:\Users\.m2\repository\com\sun\jersey\jersey-project\1.2\jersey-project-1.2.pom

the POM content maybe incorrect, like following,

<html>
<head><title>301 Moved Permanently</title></head>
<body bgcolor="white">
<center><h1>301 Moved Permanently</h1></center>
<hr><center>nginx/0.6.39</center>
</body>
</html

just delete the POM file(or just delet jersey directory), and re-try, you will fix this problem

score 0 · Answer 3 · edited May 23 '17 at 12:00

0

Refer this answer https://stackoverflow.com/a/27248395/1122841

As suggested there I added mirroring details in settings.xml (inside config directory of maven) deleted .m2/repository/com/sun/jersey so that previously downloaded jars or poms are deleted And built project again. It freshly downloaded all things successfully.

edited May 23 '17 at 12:00

Community

1
1

answered Mar 17 '15 at 08:15

Kaushik Lele

6,439
13
50
76

maven build failed for glassfish dependency

3 Answers3