[
https://issues.apache.org/jira/browse/MDEPLOY-36?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17965619#comment-17965619
]
Olivier Lamy commented on MDEPLOY-36:
-------------------------------------
This project has moved from Jira to GitHub Issues. This issue was migrated to
[apache/maven-deploy-plugin#263|https://github.com/apache/maven-deploy-plugin/issues/263].
> Custom ArtifactRepositoryLayouts confuse deploy-file
> ----------------------------------------------------
>
> Key: MDEPLOY-36
> URL: https://issues.apache.org/jira/browse/MDEPLOY-36
> Project: Maven Deploy Plugin (Moved to GitHub Issues)
> Issue Type: Bug
> Affects Versions: 2.2
> Reporter: Matthew Beermann
> Priority: Major
>
> We've created some custom ArtifactRepositoryLayouts. They work just fine, but
> they seem to confuse the deploy-file goal. In particular, if the custom
> layout is present in maven-2.0.4\libs, then it will cause deploy-file to
> _always_ use the "legacy" layout, regardless of the value of
> -DrepositoryLayout.
> I'm pretty sure our custom ArtifactRepositoryLayout is written correctly, but
> just in case, here's the contents of components.xml:
> <component-set>
> <components>
> <component>
>
> <role>org.apache.maven.artifact.repository.layout.ArtifactRepositoryLayout</role>
> <role-hint>eclipse</role-hint>
>
> <implementation>org.apache.maven.artifact.repository.layout.EclipseRepositoryLayout</implementation>
> </component>
> </components>
> </component-set>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
