Return-Path: X-Original-To: apmail-maven-issues-archive@minotaur.apache.org Delivered-To: apmail-maven-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 5AE00193D0 for ; Sat, 23 Apr 2016 12:02:13 +0000 (UTC) Received: (qmail 16264 invoked by uid 500); 23 Apr 2016 12:02:13 -0000 Delivered-To: apmail-maven-issues-archive@maven.apache.org Received: (qmail 16197 invoked by uid 500); 23 Apr 2016 12:02:13 -0000 Mailing-List: contact issues-help@maven.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@maven.apache.org Delivered-To: mailing list issues@maven.apache.org Received: (qmail 16168 invoked by uid 99); 23 Apr 2016 12:02:13 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 23 Apr 2016 12:02:13 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id E75012C1F5A for ; Sat, 23 Apr 2016 12:02:12 +0000 (UTC) Date: Sat, 23 Apr 2016 12:02:12 +0000 (UTC) From: "Karl Heinz Marbaise (JIRA)" To: issues@maven.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Comment Edited] (MJAR-183) Move LifecycleMapping and ArtifactHandler from maven-core to target packaging plugin MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/MJAR-183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15255239#comment-15255239 ] Karl Heinz Marbaise edited comment on MJAR-183 at 4/23/16 12:01 PM: -------------------------------------------------------------------- For testings purposes I have created a special Maven Core (current master of maven) where i removed the whole mapping information in the {{default-bindings.xml}} for {{maven-jar-plugin}} and tried to compile a usual test project which of course failed. After adding {{maven-jar-plugin}} with {{true}} is simply works. To write an integration tests within the {{maven-jar-plugin}} seemed to be impossible cause turning of plugin bindings from the life cycle are only possible using the correct id's which are also uses by the bindings in maven-jar-plugin which results in not working the whole. was (Author: khmarbaise): I have create a special Maven Core where i removed the whole mapping information in the {{default-bindings.xml}} for maven-jar-plugin and tried to compile a usual test project which of course failed. After adding maven-jar-plugin with {{true}} is simply works. To write an integration tests within the maven-jar-plugin seemed to be impossible cause turning of plugin bindings from the life cycle are only possible using the correct id's which are also uses by the bindings in maven-jar-plugin which results in not working the whole. > Move LifecycleMapping and ArtifactHandler from maven-core to target packaging plugin > ------------------------------------------------------------------------------------ > > Key: MJAR-183 > URL: https://issues.apache.org/jira/browse/MJAR-183 > Project: Maven JAR Plugin > Issue Type: Improvement > Reporter: Robert Scholte > > Maven Core shouldn't be aware of this kind of information, instead the maven-jar-plugin should specify and maintain the {{LifecycleMapping}} and {{ArtifactHandler}} by itself. -- This message was sent by Atlassian JIRA (v6.3.4#6332)