[
http://jira.codehaus.org/browse/MRM-376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_97666
]
Maria Odea Ching commented on MRM-376:
--------------------------------------
Re: MRM-402
I found out that the problem with the commons-dbcp-1.0 artifact was that its
version in the pom is '1.0-dev', but when you browse that artifact from the
results page.. the version that is queried is '1.0' thus the
JDOObjectNotFoundException. Is this still an archiva problem? or is it with the
pom.
Also, I found out that some artifacts that have parent projects are getting the
same error JDOObjectNotFoundException because it wasn't added to the database
due to a 'null' origin field. I think the problem is during the merging of the
parent poms. Will comment more on this issue later on.
> Clicking an artifact in the Search Results page results to HTTP ERROR: 500
> --------------------------------------------------------------------------
>
> Key: MRM-376
> URL: http://jira.codehaus.org/browse/MRM-376
> Project: Archiva
> Issue Type: Bug
> Components: browser
> Reporter: Dawn Angelito
> Assignee: Maria Odea Ching
> Priority: Blocker
> Fix For: 1.0-alpha-1
>
>
> Steps:
> 1) On the left menu, under Find, click Search.
> 2) Enter a keyword that you want to search. (e.g. ant)
> 3) Click Submit. The search results will be displayed.
> 4) Click an artifact from the list. (In my case, I clicked "ant".)
> Resulted to:
> HTTP ERROR: 500
> Unable to find Database Object [ant:ant:1.6::pom] of type
> org.apache.maven.archiva.model.ArchivaArtifactModel using no fetch-group
> RequestURI=/archiva/browse/ant/ant/1.6
--
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
