[
http://jira.codehaus.org/browse/MRM-659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=129795#action_129795
]
Thomas Demande commented on MRM-659:
------------------------------------
>From a Maven 2 project, when I try to get a Maven 1 ejb artifact _via_
>Archiva, it's still trying to get it from
>_groupId_/*jars*/_artifactId_-_version_.jar.
I'm using newly packaged 1.0.2 version you're voting for (from
http://people.apache.org/builds/maven/archiva/1.0.2/), that should resolve the
problem according to this issue fix version.
Did I miss some configuration steps ?
> 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
