From dev-return-7290-archive-asf-public=cust-asf.ponee.io@groovy.apache.org Wed Mar 31 12:39:56 2021 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mxout1-he-de.apache.org (mxout1-he-de.apache.org [95.216.194.37]) by mx-eu-01.ponee.io (Postfix) with ESMTPS id B3EE3180607 for ; Wed, 31 Mar 2021 14:39:56 +0200 (CEST) Received: from mail.apache.org (mailroute1-lw-us.apache.org [207.244.88.153]) by mxout1-he-de.apache.org (ASF Mail Server at mxout1-he-de.apache.org) with SMTP id 0D5E46010B for ; Wed, 31 Mar 2021 12:39:55 +0000 (UTC) Received: (qmail 9866 invoked by uid 500); 31 Mar 2021 12:39:55 -0000 Mailing-List: contact dev-help@groovy.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@groovy.apache.org Delivered-To: mailing list dev@groovy.apache.org Delivered-To: moderator for dev@groovy.apache.org Received: (qmail 8705 invoked by uid 99); 31 Mar 2021 12:38:53 -0000 Message-ID: From: Mariusz W References: Subject: Re: Potential removal of JAXB un/marshal extension methods in Groovy 4 x-ponymail-sender: aa671f74073c1a07fabb0475027f6ac61be7326e MIME-Version: 1.0 Date: Wed, 31 Mar 2021 12:38:52 -0000 x-ponymail-agent: PonyMail Composer/0.2 To: In-Reply-To: Content-Type: text/plain; charset=utf-8 X-Mailer: LuaSocket 3.0-rc1 Hi, Ok for me. I still had to remember to add / copy dependency files from extras-jaxb. As I understand it will no longer be needed. Regards, Mariusz On 2021/03/29 06:14:30, Paul King wrote: > Hi folks, > > We have 4 JAXB extension methods which offer a very small enhancement over > the built-in JAXB methods. The way these are packaged causes increased > complexity in JDK9+ environments which even today doesn't seem to be > handled well by IDEs such as JetBrains' IDEA. Weighing up the minimal value > those methods add vs the complexities they burden us with, I am thinking of > removing those methods in Groovy 4. Does anyone have objections? > > The groovy-jaxb jar from Groovy 3 will likely remain compatible with Groovy > 4 for those that still wish this functionality but folks would need to > explicitly add that as a dependency. Feedback welcome. > > Cheers, Paul. >