[jira] Commented: (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:comment-tabpanelfocusedCommentId=189472#action_189472 ] Gabriel Dogaru commented on MNG-4238: - I am using extensionstrue/extensions. This happens if I use @requiresDependencyResolution test and my dependency has test scope. If I use compile for the dependency scope the artifact appears in the list of projects artifacts. 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 Assignee: 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
[jira] Commented: (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:comment-tabpanelfocusedCommentId=189380#action_189380 ] Gabriel Dogaru commented on MNG-4238: - I am using maven 2.2.1 and I have the same problem for a custom ArtifactHandler define by the plugin that provides estensions. When I use in my mojo @requiresDependencyResolution test and i call projects.artifacts it gets all the artifacts for test(including junit others) but not my custom artifact type. 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 Assignee: 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
[jira] Commented: (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:comment-tabpanelfocusedCommentId=189382#action_189382 ] John Casey commented on MNG-4238: - You have to set extensionstrue/extensions on the plugin that provides the artifact handler, or it won't be loaded. 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 Assignee: 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
