[ 
https://issues.apache.org/jira/browse/MRM-1859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15969299#comment-15969299
 ] 

Hudson commented on MRM-1859:
-----------------------------

SUCCESS: Integrated in Jenkins build archiva-master-build #988 (See 
[https://builds.apache.org/job/archiva-master-build/988/])
[MRM-1859] Improve handling of invalid artifacts (martin_s: 
[https://github.com/apache/archiva/commit/94e8342ec044224226a53efc090ccb4d31d4b94b])
* (add) 
archiva-modules/plugins/maven2-repository/src/test/resources/test01.properties
* (edit) archiva-modules/plugins/maven2-repository/pom.xml
* (edit) 
archiva-modules/plugins/maven2-repository/src/main/java/org/apache/archiva/metadata/repository/storage/maven2/Maven2RepositoryStorage.java
* (edit) 
archiva-modules/plugins/maven2-repository/src/test/java/org/apache/archiva/metadata/repository/storage/maven2/Maven2RepositoryMetadataResolverTest.java
* (edit) 
archiva-modules/plugins/maven2-repository/src/test/java/org/apache/archiva/dependency/tree/maven2/DependencyTreeBuilderTestMaven3.java
* (add) 
archiva-modules/plugins/maven2-repository/src/test/resources/resolver-status.properties


> Error upon viewing 'Artifacts' tab when browsing an artifact 
> -------------------------------------------------------------
>
>                 Key: MRM-1859
>                 URL: https://issues.apache.org/jira/browse/MRM-1859
>             Project: Archiva
>          Issue Type: Bug
>    Affects Versions: 2.1.1
>            Reporter: Maria Odea Ching
>            Assignee: Maria Odea Ching
>             Fix For: 2.2.2
>
>         Attachments: archiva_mrm_1859_bug.png
>
>
> The following error shows up in the logs:
> {quote}
> org.apache.cxf.interceptor.Fault: Not a valid artifact path in a Maven 2 
> repository, filename 'resolver-status.properties' doesn't start with artifact 
> ID 'my-app-isat'
> {quote}
> Upon investigating, properties files are not included in the filter when 
> retrieving the list of artifacts in the repository directory causing the 
> error to occur. Only metadata, checksums, and signature files are currently 
> included in the filter.
> Additional note: the resolver-status.properties file gets created when the 
> dependency tree is built for snapshot artifacts in browse.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to