Potential removal of JAXB un/marshal extension methods in Groovy 4

[Paul King <pa...@asert.com.au>]

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.

Re: Potential removal of JAXB un/marshal extension methods in Groovy 4

[Paul King <pa...@asert.com.au>]

On Wed, Mar 31, 2021 at 10:39 PM Mariusz W <ma...@gmail.com> wrote:

> 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.
>

Yes, those jars should be added transitively by your build tool if you have
groovy-jaxb as dependency and should be added automatically when needed if
you are using the start scripts that come with a Groovy install or standard
groovy-starter.conf file in the Groovy install but there has been mixed
support from IDE vendors as to whether those jars are added automatically
or must be manually added - obviously it depends on which JDK versions are
in use etc, so I guess involves some complexity.

For those interested, there are now further links.

Jira: https://issues.apache.org/jira/browse/GROOVY-10005
PR: https://github.com/apache/groovy/pull/1539

Cheers, Paul.


> Regards,
> Mariusz
>
> On 2021/03/29 06:14:30, Paul King <pa...@asert.com.au> 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.
> >
>

Re: Potential removal of JAXB un/marshal extension methods in Groovy 4

[Mariusz W <ma...@gmail.com>]

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 <pa...@asert.com.au> 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.
>