[
http://jira.codehaus.org/browse/MRM-659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=129972#action_129972
]
Brett Porter commented on MRM-659:
----------------------------------
you're right, sorry. The managed repository can be set to either, but to pass
an ejb request to the legacy remote repository requires the incoming request to
be in legacy format. This is because of the erasure of information in the Maven
2 repository format.
> archiva cannot serve ejb artifacts from a maven1 repository
> -----------------------------------------------------------
>
> Key: MRM-659
> URL: http://jira.codehaus.org/browse/MRM-659
> Project: Archiva
> Issue Type: Bug
> Components: remote proxy
> Affects Versions: 1.0
> Reporter: nicolas de loof
> Assignee: Brett Porter
> Fix For: 1.0.2
>
>
> requesting an ejb from a maven1 repository builds the path
> "groupId/jars/artifactId.jar", and not the location where maven1 ejb:deploy
> places the ejb jars (groupId/ejbs/artifactId.jar). The type folder is created
> based on the file extension, with some exceptions. It should be created based
> on the artifact type.
--
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
