I’m quite sure those sources are related to GWT, as we known GWT requires source to transpile.
Need assess the dependency and the feasibility to even remove the GWT component. I’m +1 to evaluate all GWT related components removal - we can always depend on older version while we catchup with new development to replace those. - Alex On Wed, Jul 23, 2025 at 7:26 AM Enrique Gonzalez Martinez < [email protected]> wrote: > I dont see any problem to include this. If this is impacts gwt stuff.. > probably somebody with more knowledge should twist and shout how feasible > is this. > > > El mié, 23 jul 2025, 9:53, Toni Rikkola <[email protected]> escribió: > > > Hi, > > > > Currently we have XML and JSON Mapper libraries in KIE that are > > duplicates of identical libraries outside of our code base. The reason > > for forking them in was likely due to an old requirement that we need to > > control all the source at KIE, here at Apache or back at Red Hat. At > > this moment this is not true, if it ever was. > > > > Problem is these libraries are licensed under GPL and if GPL is used > > inside an ASL project it consumes everything and the project is then GPL. > > > > The plan is to remove our fork and use the originals with the GPL > > linking exception. > > > > > > Related ticket: > https://github.com/apache/incubator-kie-tools/issues/3196 > > > > Related dev list thread: > > https://lists.apache.org/thread/gsj0mxkzwpcgwztz231tr6tnnx9kxd0g > > > > Linking exception: > > https://openjdk.org/legal/gplv2+ce.html > > https://en.wikipedia.org/wiki/GPL_linking_exception > > > > > > Toni Rikkola > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > >
