[
http://jira.codehaus.org/browse/MRM-207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brett Porter closed MRM-207.
----------------------------
Assignee: Brett Porter (was: Henri Yandell)
Resolution: Won't Fix
Fix Version/s: (was: 1.0.x)
no longer relevant to trunk
> POM error when indexing an m1 repository
> ----------------------------------------
>
> Key: MRM-207
> URL: http://jira.codehaus.org/browse/MRM-207
> Project: Archiva
> Issue Type: Bug
> Components: indexing
> Reporter: Henri Yandell
> Assignee: Brett Porter
>
> org.apache.maven.project.InvalidProjectModelException: Not a v4.0.0 POM.
>
> org.apache.maven.project.DefaultMavenProjectBuilder.readModel(DefaultMavenProjectBuilder.java:1299)
>
> org.apache.maven.project.DefaultMavenProjectBuilder.readModel(DefaultMavenProjectBuilder.java:1270)
>
> org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepository(DefaultMavenProjectBuilder.java:471)
>
> org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepository(DefaultMavenProjectBuilder.java:225)
>
> org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepository(DefaultMavenProjectBuilder.java:235)
>
> org.apache.maven.archiva.web.action.ShowArtifactAction.readProject(ShowArtifactAction.java:257)
>
> org.apache.maven.archiva.web.action.ShowArtifactAction.artifact(ShowArtifactAction.java:127)
> So seems pretty simple - Archiva is looking for m2 poms in the m1 repository.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
