Lukas Jungmann

> Yes but currently they are not mandated, maybe they never will? Read what I'm asking for once again, please. I'm by no means saying that support for OSGi must...

> If the document @ivargrimstad mentioned will become part of the Jakarta EE 10 deliverables or published in some form, sure, but I don't think it's enough to only discuss...

What warning do you mean? Can you attach (or link) simple reproducer for this? thanks

> Hope you solve the problem with JDK 21 compatibility because it's not working till now has a lot of issues and bugs I have no idea what are you...

> @lukasj is there a plan to refactor out the usage of deprecated `URL` constructors? removing deprecated (not-only JDK) APIs is an on-going incremental process (see ie [this PR](https://github.com/eclipse-ee4j/metro-jax-ws/pull/323)), so...

I'd rather see them finally removed instead. Also note that this is not the project being responsible for them nor defining them

it's safe to use newer version of [woodstox 6.5.1](https://mvnrepository.com/artifact/com.fasterxml.woodstox/woodstox-core/6.5.1), which is an external dependency

see https://bugs.openjdk.java.net/browse/JDK-8231578 - there is not much we can do unless someone provides a PR workarounding this...

this comes from jaxb-ri as `JAXBContext context = JAXBContext.newInstance(Greeting.class, GreetingImpl.class, GreetingImpl.Adapter.class);` fails as well

v3 and v4 are not fully compatible - see https://github.com/jakartaee/jaxb-api/releases which lists some breaking changes to make the test in the project passing: - update test: ``` @Test public void...