Uploaded image for project: 'Maven'
  1. Maven
  2. MNG-5697

remove LifecycleMapping and ArtifactHandler from maven-core: move to target packaging plugin

Attach filesAttach ScreenshotAdd voteVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Open
    • Major
    • Resolution: Unresolved
    • None
    • 4.x / Backlog
    • Plugins and Lifecycle
    • None

    Description

      Maven Core should only be aware of the pom packaging details, the rest of the ArtifactHandlers and LifecycleMappings should be moved to their own packaging plugin:

      • jar packaging: maven-jar-plugin
      • ejb and ejb3 packagings: maven-ejb-plugin
      • maven-plugin packaging: maven-plugin-plugin
      • war packaging: maven-war-plugin
      • ear packaging: maven-ear-plugin
      • rar packaging: maven-rar-plugin
      • par packaging: ?

      LifecycleMappings http://maven.apache.org/ref/3.2.5/maven-core/default-bindings.html
      ArtifactHandlers http://maven.apache.org/ref/3.2.5/maven-core/artifact-handlers.html

      Maven core should then get the lifecycle mappings and artifact handlers configurations from the plugin at the beginning of the build, before begin able to calculate the build plan

      Attachments

        Issue Links

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            Unassigned Unassigned
            rfscholte Robert Scholte

            Dates

              Created:
              Updated:

              Slack

                Issue deployment