Maven
  1. Maven
  2. MNG-4238

Custom ArtifactHandler provided by build extension isn't used for project artifact

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 2.2.0
    • Fix Version/s: 2.2.1
    • Labels:
      None

      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.

        Activity

        No work has yet been logged on this issue.

          People

          • Assignee:
            John Casey
            Reporter:
            John Casey
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development