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 C8EB517F67 for ; Sun, 1 Mar 2015 15:46:04 +0000 (UTC) Received: (qmail 98751 invoked by uid 500); 1 Mar 2015 15:46:04 -0000 Delivered-To: apmail-cxf-issues-archive@cxf.apache.org Received: (qmail 98706 invoked by uid 500); 1 Mar 2015 15:46:04 -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 98695 invoked by uid 99); 1 Mar 2015 15:46:04 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 01 Mar 2015 15:46:04 +0000 Date: Sun, 1 Mar 2015 15:46:04 +0000 (UTC) From: "ASF GitHub Bot (JIRA)" To: issues@cxf.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (CXF-6268) Make cxf-codegen-plugin toolchains aware during maven build 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-6268?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14342292#comment-14342292 ] ASF GitHub Bot commented on CXF-6268: ------------------------------------- GitHub user kops opened a pull request: https://github.com/apache/cxf/pull/55 CXF-6268 Make cxf-codegen-plugin toolchains aware during maven build Support toolchains configuration during java code generation. When _fork_ parameter is enabled, 1. use provided javaExecutable path if available 2. use toolchains configuration if available 3. use default `${java.home}/bin/java` I added a maven-invoker-plugin to run a simple test using toolchains. You can merge this pull request into a Git repository by running: $ git pull https://github.com/kops/cxf 2.6.x-toolchains Alternatively you can review and apply these changes as the patch at: https://github.com/apache/cxf/pull/55.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #55 ---- commit 16f270e86b40355649aff59b9893e1fd9eb62373 Author: kops Date: 2015-02-25T01:16:54Z CXF-6268 Add toolchains support to codegen-plugin Default behavior is modified and the javaExecutable path is resolved in the following order: 1. a 'javaExecutable' property explicitely set is used as is ; 2. if the the toolchain manager provides a 'jdk' then it is used ; 3. fallback to default behavior: ${java.home}/bin/java. commit e3322c7f25d8c296e3acc8cd85020eba26106632 Author: kops Date: 2015-03-01T15:26:27Z CXF-6268 Add integration test commit 79b42fee70ddc13346606cbab874ac8e5d6dc5da Author: kops Date: 2015-02-25T01:18:37Z fix unused import ---- > Make cxf-codegen-plugin toolchains aware during maven build > ----------------------------------------------------------- > > Key: CXF-6268 > URL: https://issues.apache.org/jira/browse/CXF-6268 > Project: CXF > Issue Type: Improvement > Affects Versions: 2.6.16, 3.0.4, 2.7.15 > Reporter: Jeremie H > > I'm working on a project built with Java 1.6. I though it could be a good idea to set up the {{maven-toolchains-plugin}}. > Unfortunately the {{cxf-codegen-plugin}} uses the java available in the {{java.home}} system property. Although this can be configured with the {{javaExecutable}} property of the mojo, it generates configuration duplication. > https://cwiki.apache.org/confluence/display/MAVENOLD/Toolchains seems to show an easy way to do that. -- This message was sent by Atlassian JIRA (v6.3.4#6332)