You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Henri Yandell (JIRA)" <ji...@codehaus.org> on 2006/10/07 00:16:29 UTC
[jira] Created: (MRM-207) POM error when indexing an m1 repository
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
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
[jira] Closed: (MRM-207) POM error when indexing an m1 repository
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ 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
[jira] Commented: (MRM-207) POM error when indexing an m1
repository
Posted by "Henri Yandell (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-207?page=comments#action_76849 ]
Henri Yandell commented on MRM-207:
-----------------------------------
I'm not sure if this happened while indexing actually - I think the bug in indexing was:
2006-10-06 15:26:38,343 [http-8080-Processor24] INFO RepositoryTask:indexer - Searching repository OsJava SVN repository
2006-10-06 15:26:39,527 [http-8080-Processor24] ERROR DispatcherUtils - Could not execute action
java.lang.NullPointerException
at org.apache.maven.archiva.scheduler.task.IndexerTask.execute(IndexerTask.java:215)
at org.apache.maven.archiva.scheduler.task.IndexerTask.execute(IndexerTask.java:122)
at org.apache.maven.archiva.scheduler.DefaultRepositoryTaskScheduler.runIndexer(DefaultRepositoryTaskScheduler.java:175)
at org.apache.maven.archiva.web.action.admin.RunRepositoryTaskAction.runIndexer(RunRepositoryTaskAction.java:45)
I think the one above was when it came time to view the loaded artifact. Will retest.
> 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
>
> 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
[jira] Updated: (MRM-207) POM error when indexing an m1 repository
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-207?page=all ]
Brett Porter updated MRM-207:
-----------------------------
Fix Version/s: 1.0
> 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
> Assigned To: Henri Yandell
> Fix For: 1.0
>
>
> 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