Return-Path: X-Original-To: apmail-cxf-issues-archive@www.apache.org Delivered-To: apmail-cxf-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 9DD11F0C1 for ; Mon, 15 Apr 2013 01:11:13 +0000 (UTC) Received: (qmail 55881 invoked by uid 500); 15 Apr 2013 01:11:13 -0000 Delivered-To: apmail-cxf-issues-archive@cxf.apache.org Received: (qmail 55847 invoked by uid 500); 15 Apr 2013 01:11:13 -0000 Mailing-List: contact issues-help@cxf.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cxf.apache.org Delivered-To: mailing list issues@cxf.apache.org Received: (qmail 55838 invoked by uid 99); 15 Apr 2013 01:11:13 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 15 Apr 2013 01:11:13 +0000 Date: Mon, 15 Apr 2013 01:11:13 +0000 (UTC) From: "Freeman Fang (JIRA)" To: issues@cxf.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Assigned] (CXF-4962) change plugin in cxf-jaxws-javafirst archtype 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/CXF-4962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Freeman Fang reassigned CXF-4962: --------------------------------- Assignee: Freeman Fang > change plugin in cxf-jaxws-javafirst archtype > --------------------------------------------- > > Key: CXF-4962 > URL: https://issues.apache.org/jira/browse/CXF-4962 > Project: CXF > Issue Type: Improvement > Components: Tooling > Reporter: Marco Westermann > Assignee: Freeman Fang > > The cxf-jaxws-javafirst archtype includes the tomcat-maven-plugin. But it still uses the old one from codehaus.mojo. IMHO it should use the org.apache.tomcat.maven/tomcat6-maven-plugin/2.1 version. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira