Lukas Jungmann

@fperezel yaml file allows comment - is there any reason to not include license header in this file?

@fperezel I usually add the license the project itself is said to use, so in this particular case it should be an EPL-2.0 OR GPL-2.0 WITH Classpath-exception-2.0, see ie [the...

with jaxb, they can co-exist on the same classpath as long as they use jaxb-ri. Ie in Metro, the problem there was xmlsec dependent on javax with GlassFish having jakarta....

> > The solution I used was to repackage javax versions in an extra artifact > > If I understand correctly, repackaging javax versions allowed those apps to have both...

>> If there was a bundling of `jakarta.xml.bind-api` > no, I'm not aware of such artifact. I mean apart from Java EE 8 versions of those artifacts obviously, which are...

> I'm interested to understand why do we say this would be the worst solution? since: ```xml javax.xml.bind jaxb-api 2.3.2 com.sun.xml.bind jaxb-impl 2.3.6 jakarta.xml.bind jakarta.xml.bind-api 4.0.0 org.glassfish.jaxb jaxb-runtime 4.0.0 ```...

@winne42 feel free to propose a solution you want to see

issues in [xml binding spec](https://jakarta.ee/specifications/xml-binding/3.0/jakarta-xml-binding-spec-3.0.html) are covered in #346 issues in jsonp were fixed at source by https://github.com/eclipse-ee4j/jsonp/pull/272, ~~update for the web (jsonp service release) will follow~~ covered by https://github.com/jakartaee/specifications/pull/343

as requested, thanks!

Whatever you think is the best, I only need to know where to (re-)create this PR... One drawback I can see is in syncing changes between those two repos. On...