[
http://jira.codehaus.org/browse/MRM-143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_99181
]
Maria Odea Ching commented on MRM-143:
--------------------------------------
A jar is corrupted when:
- it is not readable
- the jar's filename does not match it's pom's artifactId and version (pom
included in the jar)
- the files inside the jar file are not readable (?)
A pom is corrupted when:
- it is not readable
- the pom file itself does not match the artifactId and version in its content
- the pom file does not match its corresponding jar file (if present)
Are there other things that were not included above?
And are the metadata and checksum files also included here?
> improve error reporting on corrupt jars, poms, etc
> --------------------------------------------------
>
> Key: MRM-143
> URL: http://jira.codehaus.org/browse/MRM-143
> Project: Archiva
> Issue Type: Improvement
> Components: indexing
> Reporter: Brett Porter
> Assignee: Maria Odea Ching
> Fix For: 1.0-alpha-2
>
>
> currently, many failures can be detected during indexing but none are
> reported anywhere other than the logs. Either these need to be sent through
> the regular reporting mechanism, or the regular reporting mechanism needs to
> be able to come back later and pick up the same issues.
--
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
