You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Matthew Beermann (JIRA)" <ji...@codehaus.org> on 2007/04/25 00:14:26 UTC
[jira] Closed: (MDEPLOY-36) Custom ArtifactRepositoryLayouts
confuse deploy-file
[ http://jira.codehaus.org/browse/MDEPLOY-36?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matthew Beermann closed MDEPLOY-36.
-----------------------------------
Resolution: Won't Fix
Fix Version/s: (was: 2.4)
Withdrawing this request, as we no longer need it.
> Custom ArtifactRepositoryLayouts confuse deploy-file
> ----------------------------------------------------
>
> Key: MDEPLOY-36
> URL: http://jira.codehaus.org/browse/MDEPLOY-36
> Project: Maven 2.x Deploy Plugin
> Issue Type: Bug
> Affects Versions: 2.2
> Reporter: Matthew Beermann
>
> 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 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