Mailing-List: contact issues-help@cxf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cxf.apache.org
Date: Tue, 25 Aug 2015 12:43:45 +0000 (UTC)
From: "Victor (JIRA)" <jira@apache.org>
To: issues@cxf.apache.org
Message-ID: <JIRA.12858607.1440506620000.158602.1440506625647@Atlassian.JIRA>
In-Reply-To: <JIRA.12858607.1440506620000@Atlassian.JIRA>
References: <JIRA.12858607.1440506620000@Atlassian.JIRA>
 <JIRA.12858607.1440506620674@arcas>
Subject: [jira] [Created] (CXF-6556) Make all maven plugins m2e compatible
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

Victor created CXF-6556:
---------------------------

             Summary: Make all maven plugins m2e compatible
                 Key: CXF-6556
                 URL: https://issues.apache.org/jira/browse/CXF-6556
             Project: CXF
          Issue Type: Improvement
          Components: Tooling
    Affects Versions: 3.1.2
            Reporter: Victor
            Priority: Minor


Hi,

In the same manner that CXF-4152 was fixed, it would be nice if the other m=
aven plugins were compatible with m2e, i.e. introduce a lifecycle mapping f=
ile like the codegen-plugin one: https://svn.apache.org/repos/asf/cxf/trunk=
/maven-plugins/codegen-plugin/src/main/resources/META-INF/m2e/lifecycle-map=
ping-metadata.xml

It makes at least sense for the java2ws-plugin, but maybe also for the othe=
rs (I=C2=A0don't use them...).


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)