[MNG-4238] Custom ArtifactHandler provided by build extension isn't used for project artifact

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.2.0
• Fix Version/s: 2.2.1
• Component/s: Artifacts and Repositories
• Assignee: John Dennis Casey
• Reporter: John Dennis Casey
• Created: 13/Jul/09 18:29
• Updated: 02/Sep/09 02:37
• Resolved: 13/Jul/09 18:37

Description

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.