Return-Path: X-Original-To: apmail-cxf-dev-archive@www.apache.org Delivered-To: apmail-cxf-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 3CC9F113C8 for ; Mon, 19 May 2014 22:14:00 +0000 (UTC) Received: (qmail 79722 invoked by uid 500); 19 May 2014 22:14:00 -0000 Delivered-To: apmail-cxf-dev-archive@cxf.apache.org Received: (qmail 79663 invoked by uid 500); 19 May 2014 22:14:00 -0000 Mailing-List: contact dev-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 dev@cxf.apache.org Received: (qmail 79655 invoked by uid 99); 19 May 2014 22:14:00 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 19 May 2014 22:14:00 +0000 X-ASF-Spam-Status: No, hits=2.2 required=5.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [72.249.186.197] (HELO sosnoski.com) (72.249.186.197) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 19 May 2014 22:13:54 +0000 Received: from linux-a5lu.site (ip-58-28-158-218.static-xdsl.xnet.co.nz [58.28.158.218]) by sosnoski.com (Postfix) with ESMTPSA id E90C41008D for ; Mon, 19 May 2014 22:13:29 +0000 (UTC) Message-ID: <537A8207.8020104@sosnoski.com> Date: Tue, 20 May 2014 10:13:27 +1200 From: Dennis Sosnoski User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0 MIME-Version: 1.0 To: dev@cxf.apache.org Subject: Re: [DISCUSS] Short term plans/branching.... References: <330026BE-3799-4F6D-8459-092B03295F8F@apache.org> <689760432.20140519145451@gmail.com> <7B582DCE-AA0E-4816-B6A3-1A1467A03751@apache.org> In-Reply-To: <7B582DCE-AA0E-4816-B6A3-1A1467A03751@apache.org> Content-Type: multipart/alternative; boundary="------------060802070900050607050806" X-Virus-Checked: Checked by ClamAV on apache.org --------------060802070900050607050806 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 8bit I don't think the JiBX support should be any concern. I haven't been maintaining the JiBX code for some time, and the Java 8 issue is probably the last nail in the coffin. A new release of BCEL might let JiBX limp along a little longer, but BCEL has been obsolete for a long time. I would have liked to strip out the BCEL usage and replace it with ASM, which would also have been cause to clean up some of the nastiest code in the project, but without some financial support that's not going to happen. So I'd say just drop JiBX support going forward. - Dennis On 05/20/2014 07:26 AM, Daniel Kulp wrote: > On May 19, 2014, at 2:54 PM, Andriy Redko wrote: > >> >Hi Dan, >> > >> >Excellent plan! One question though: following recent discussions on the list, >> >there is strong interest in Java 8 support but we know some issues have to be resolved. >> >Do you think we can at least investigate Java 8 support and be ready as much as we can? > I know Willem and I have both been doing a bunch of experiments with Java8. The main blocker we have right now is all the JIBX related stuff as the JIBX plugin cannot work with Java8. It�s pretty much out of our hands (and not really even in the JIBX�s folks hands) as it would require a release of BCEL from the Apache Commons folks first. I*think* if a BCEL release was made, we could at least build CXF with Java8. That would leave a couple remaining issues: --------------060802070900050607050806--