[
http://jira.codehaus.org/browse/MRM-517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
nicolas de loof updated MRM-517:
--------------------------------
Attachment: MRM-517.patch
Add an optional parameter to splitFilename for supposed version. In such case,
the version String can contain any char, even not a valid
VersionUtil.versionPatterns.
This can solve this issue for m2 requests, but will make the artifact not
available to m1, until m1 artifact - version is splitted a more robust way.
> Some maven 2 requests are treated as maven 1 requests
> -----------------------------------------------------
>
> Key: MRM-517
> URL: http://jira.codehaus.org/browse/MRM-517
> Project: Archiva
> Issue Type: Bug
> Affects Versions: 1.0-beta-2, 1.0-beta-3
> Reporter: James William Dumay
> Assignee: Joakim Erdfelt
> Fix For: 1.0-beta-3
>
> Attachments: error.txt, MRM-517.patch
>
>
> We requested the following artifact's from our public Archiva instance which
> resulted in the attached error.txt
> fop:fop:trunk-534713-atlassian -
> https://maven.atlassian.com/repository/public/fop/fop/trunk-534713-atlassian/fop-trunk-534713-atlass
> org.hibernate:jtidy:r8-21122004 -
> https://maven.atlassian.com/repository/public/org/hibernate/jtidy/r8-21122004/jtidy-r8-21122004.jar
> Brett looked at this and said that Archiva is interpreting both of these urls
> as maven1 requests and breaking.
--
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
