You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "John Casey (JIRA)" <ji...@codehaus.org> on 2009/07/14 01:30:22 UTC
[jira] Updated: (MNG-4238) Custom ArtifactHandler provided by build
extension isn't used for project artifact
[ http://jira.codehaus.org/browse/MNG-4238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
John Casey updated MNG-4238:
----------------------------
Fix Version/s: 2.2.1
> Custom ArtifactHandler provided by build extension isn't used for project artifact
> ----------------------------------------------------------------------------------
>
> Key: MNG-4238
> URL: http://jira.codehaus.org/browse/MNG-4238
> Project: Maven 2
> Issue Type: Bug
> Components: Artifacts and Repositories
> Affects Versions: 2.2.0
> Reporter: John Casey
> Fix For: 2.2.1
>
>
> If I reference a build extension which provides a custom ArtifactHandler, then set the packaging for the project so that it should use the custom ArtifactHandler when it installs, I find that a default on-demand ArtifactHandler is used instead.
> Looking at this more closely, it appears that ArtifactHandlers brought in by extensions (NOT plugins with extensions == true) are never registered with the already-loaded ArtifactHandlerManager. Since Maven < 3.0 doesn't support dynamic collections of components which would detect and include the new extension handler, these handlers are never used.
--
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