[jira] Commented: (MRM-409) No checking of invalid poms or artifacts during repository scanning resulting to some objects not being found on the database
[ http://jira.codehaus.org/browse/MRM-409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_100480 ] Maria Odea Ching commented on MRM-409: -- Validation of an artifact seems to be in place in LocationArtifactsConsumer. The artifact is already being validated if it is readable, and whether it matches its pom (in the repository and the embedded pom). This consumer is not being executed since the Repository Artifact Consumers are not yet included in the configuration. I'm not sure where this configuration should be placed, though. Thoughts, anyone? > No checking of invalid poms or artifacts during repository scanning resulting > to some objects not being found on the database > - > > Key: MRM-409 > URL: http://jira.codehaus.org/browse/MRM-409 > Project: Archiva > Issue Type: Bug > Components: repository scanning >Affects Versions: 1.0-alpha-1 >Reporter: Maria Odea Ching >Assignee: Maria Odea Ching > Fix For: 1.0.x > > > See MRM-376 for more details -- 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
[jira] Commented: (MRM-409) No checking of invalid poms or artifacts during repository scanning resulting to some objects not being found on the database
[ http://jira.codehaus.org/browse/MRM-409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_99446 ] Maria Odea Ching commented on MRM-409: -- Fixed pom validation in -r547209. Validation for jars still needs to be done. For -r547209, I did the following: 1. added validation for poms in ProjectModelToDatabaseConsumer. If pom is invalid, project model is not added in the database and a new RepositoryProblem is created 2. added ObjectNotFoundException handling in ShowArtifactAction when the project model is not found on the database (display error message and redirect to generalError.jsp) 3. changed access of class FilenameParts from default to public (I've used this for the pom validation) 4. created a new class CorruptArtifactReport (related to MRM-143) that is used to identify the corrupt pom problem in #1 > No checking of invalid poms or artifacts during repository scanning resulting > to some objects not being found on the database > - > > Key: MRM-409 > URL: http://jira.codehaus.org/browse/MRM-409 > Project: Archiva > Issue Type: Bug > Components: repository scanning >Affects Versions: 1.0-alpha-1 >Reporter: Maria Odea Ching >Assignee: Maria Odea Ching > Fix For: 1.0-alpha-2 > > > See MRM-376 for more details -- 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
