You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@archiva.apache.org by "James William Dumay (JIRA)" <ji...@codehaus.org> on 2009/02/11 00:31:19 UTC
[jira] Closed: (MRM-799) Better handling of artifacts with missing
poms
[ http://jira.codehaus.org/browse/MRM-799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
James William Dumay closed MRM-799.
-----------------------------------
Resolution: Fixed
Fix Version/s: (was: 1.2)
1.2-M2
Committed :)
Thanks Jevica for the patch. I added you as a contributor to the Archiva parent pom :)
> Better handling of artifacts with missing poms
> ----------------------------------------------
>
> Key: MRM-799
> URL: http://jira.codehaus.org/browse/MRM-799
> Project: Archiva
> Issue Type: Improvement
> Affects Versions: 1.0.2
> Reporter: Wendy Smoak
> Assignee: James William Dumay
> Fix For: 1.2-M2
>
> Attachments: mrm-799-unit-test.patch, MRM-799.patch
>
>
> When there is an artifact with no pom in the repository, Archiva displays the artifact and version in 'Browse Repository' but if you
> click on the version, you get:
> Error Occurred
> * Unable to find project model for [groupId:artifactId:version]
> For example, if I delete the pom and checksums for asm:asm:3.0, [and scan and update] then I get:
> http://localhost:8080/archiva/browse/asm/asm
> Browse Repository
> [top] / asm / asm
> Versions
> 3.0/
> http://localhost:8080/archiva/browse/asm/asm/3.0
> Error Occurred
> Unable to find project model for [asm:asm:3.0].
--
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