[
http://jira.codehaus.org/browse/MRM-799?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=134248#action_134248
]
Wendy Smoak commented on MRM-799:
---------------------------------
Related thread:
http://www.nabble.com/Better-handling-of-missing-poms--td17136281.html
Brett commented: "I think it should just use a default model instead and show
the normal page so you can get the download, etc."
MRM-128 is related, and has an interesting idea: "it would be nice to consult
the pom file in the actual artifact if pom not present. (it's stored at
META-INF/maven if I recall correctly)"
> 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
>
> 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
