search

kohsuke / akuma

Embeddable daemonization library
http://akuma.kohsuke.org/
132 stars 32 forks source link

Cannot find parent: org.kohsuke:pom for project: akuma:jar:1.8 #3

Closed bradseefeld closed 11 years ago

bradseefeld commented 12 years ago

Stack trace below. Digging into this, it appears that akuma defines a repository to http://maven.glassfish, which redirects to https://maven.glassfish; however, I thought maven followed redirects such as this (albeit the SSL appears invalid at this time). Additionally, manually searching through the glassfish repo, I do not see the parent artifact anyway. I am a rookie maven user so I may have diagnosed this incorrectly.

There is a StackOverflow post that may be related: http://stackoverflow.com/questions/10168758/getting-error-reason-not-a-v4-0-0-pom-for-project-org-kohsuke-staplermaven-st

Caused by: org.apache.maven.artifact.metadata.ArtifactMetadataRetrievalException: Unable to read the metadata file for artifact 'org.kohsuke:akuma:jar': Cannot find parent: org.kohsuke:pom for project: null:akuma:jar:1.8 for project null:akuma:jar:1.8 at org.apache.maven.project.artifact.MavenMetadataSource.retrieveRelocatedProject(MavenMetadataSource.java:200) at org.apache.maven.project.artifact.MavenMetadataSource.retrieveRelocatedArtifact(MavenMetadataSource.java:94) at org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(DefaultArtifactCollector.java:387) ... 23 more Caused by: org.apache.maven.project.ProjectBuildingException: Cannot find parent: org.kohsuke:pom for project: null:akuma:jar:1.8 for project null:akuma:jar:1.8 at org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(DefaultMavenProjectBuilder.java:1396) at org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(DefaultMavenProjectBuilder.java:823) at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepository(DefaultMavenProjectBuilder.java:255) at org.apache.maven.project.artifact.MavenMetadataSource.retrieveRelocatedProject(MavenMetadataSource.java:163) ... 25 more Caused by: org.apache.maven.project.InvalidProjectModelException: Not a v4.0.0 POM. for project org.kohsuke:pom at ~/.m2/repository/org/kohsuke/pom/2/pom-2.pom at org.apache.maven.project.DefaultMavenProjectBuilder.readModel(DefaultMavenProjectBuilder.java:1599) at org.apache.maven.project.DefaultMavenProjectBuilder.readModel(DefaultMavenProjectBuilder.java:1571) at org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepository(DefaultMavenProjectBuilder.java:562) at org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(DefaultMavenProjectBuilder.java:1392) ... 28 more

And the contents of .m2/repository/org/kohsuke/pom/2/pom-2.pom:

<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>
vincentheet commented 12 years ago

I have the exact same issue with a clean project and just added akuma to it in the maven pom.xml.

vincentheet commented 12 years ago

Got it working by using maven 3 instead of version 2.

jglick commented 11 years ago

5 probably obsoletes this.

kohsuke commented 11 years ago

Marking as fixed based on @jglick's comment.