You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@archiva.apache.org by "Brett Porter (JIRA)" <ji...@codehaus.org> on 2010/02/23 12:11:55 UTC

[jira] Commented: (MRM-180) metadata reports will not detect missing metaadata files

    [ http://jira.codehaus.org/browse/MRM-180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=211258#action_211258 ] 

Brett Porter commented on MRM-180:
----------------------------------

It now reports

The artifact's POM file '.../data/repositories/test/test/MRM-675/1.0-SNAPSHOT/MRM-675-1.0-SNAPSHOT.pom' was missing

the POMs for both timestamped versions are there (but with the missing metadata it can't tell - perhaps this is just a matter of clarity?


> metadata reports will not detect missing metaadata files
> --------------------------------------------------------
>
>                 Key: MRM-180
>                 URL: http://jira.codehaus.org/browse/MRM-180
>             Project: Archiva
>          Issue Type: Bug
>          Components: reporting, repository scanning
>            Reporter: Brett Porter
>             Fix For: 1.4
>
>


-- 
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