Alright! There is no question about yes or no to shade. The right answer is yes. We always do it and we have reason for that for 13 years. Why? Because of the gson project may risk the conflicts with surefire JVM and surefire transitive dependencies. The same reason to shade Maven Shared Utils, and many other artifacts.
I was asking about the Copyright problem in Google sources. The Apache 2.0 license is legal for us. The Jackson is legal as well however it contains jackson-core, this means more than one library but that's still okay. So we have two opntions: gson and jackson. If the Copyright is not a real problem then the last test should be done with JDK 9, JDK11 and JDK 14. On Sun, Feb 23, 2020 at 3:45 PM Elliotte Rusty Harold <[email protected]> wrote: > On Sun, Feb 23, 2020 at 9:34 AM Vladimir Sitnikov > <[email protected]> wrote: > > > > >Why not using XML and built in java support? > > > > It is no longer built-in: > > > https://www.oracle.com/technetwork/java/javase/11-relnote-issues-5012449.html#JDK-8190378 > > > > What was removed was badly architected data binding packages that > caused more trouble than they were worth. Plain old reliable SAX and > DOM are still bundled as are XPath and XSLT. > > -- > Elliotte Rusty Harold > [email protected] > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
