[jira] Commented: (MRM-659) archiva cannot serve ejb artifacts from a maven1 repository
[ http://jira.codehaus.org/browse/MRM-659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=129973#action_129973 ] Thomas Demande commented on MRM-659: Well, as adding a new repository definition in legacy does the trick, I'm quite OK with that. > 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
[jira] Commented: (MRM-659) archiva cannot serve ejb artifacts from a maven1 repository
[ 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
[jira] Commented: (MRM-659) archiva cannot serve ejb artifacts from a maven1 repository
[ http://jira.codehaus.org/browse/MRM-659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=129970#action_129970 ] Thomas Demande commented on MRM-659: Well that's actually the case we have, and that's why I commented this ticket ;) > 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
[jira] Commented: (MRM-659) archiva cannot serve ejb artifacts from a maven1 repository
[ http://jira.codehaus.org/browse/MRM-659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=129969#action_129969 ] Brett Porter commented on MRM-659: -- if you have the proxied repository in legacy mode, but the managed repository in maven2 mode, then the problem will not occur - is that an option for you? > 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
[jira] Commented: (MRM-659) archiva cannot serve ejb artifacts from a maven1 repository
[ http://jira.codehaus.org/browse/MRM-659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=129966#action_129966 ] Thomas Demande commented on MRM-659: Thanks, it works by adding duplicate definition of our Archiva instance, with legacy layout specified. Anyway, I think behavior is quite strange IMHO, I would have expected that specifying the _remote repository_ as legacy would be enough, as it is the proxied repository that is in legacy mode, not the Archiva instance. > 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
[jira] Commented: (MRM-659) archiva cannot serve ejb artifacts from a maven1 repository
[ http://jira.codehaus.org/browse/MRM-659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=129912#action_129912 ] Brett Porter commented on MRM-659: -- I believe this combination can't be translated. The Maven 2 format for an ejb looks the same as a JAR, so Archiva can't know which one to return. You should have Maven 2 use the legacy format when talking to the Archiva repository so that it looks for /ejbs/* > 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
[jira] Commented: (MRM-659) archiva cannot serve ejb artifacts from a maven1 repository
[ 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
