JAX-RS 2.1.3 (Jakarta Maven Coordinates and OSGi fixes) [master]

[mkarg]

Using JAX-RS 2.1.3 (i. e. Jakarta Maven Coordinates and OSGi fixes) instead of JAX-RS 2.1 (i. e. javax Maven Coordinates).

See also #3994.

[mkarg]

It is rather obvious that Travis fails, as that service has no access to JAX-RS's private staging area. To make it run, JAX-RS MUST be released to Maven Central. Same problem as JAX-RS itself has upstream with JAXB-RI.

[jansupol]

If parent is changed to 1.0.5 and
if travis gets executed with -Pstaging,
then the Travis will run and validate the changes.
@mkarg Can you update the PR? Thank you

[mkarg]

See 3e61e75 and 7486bc0, but Travis still fails. How should Travis be able to access the private OSSRH staging area of JAX-RS? Travis is not a JAX-RS committer, so he has no access rights.

[mkarg]

@jansupol

Tests in error: JaxRsRiBundleTest.:51 » ClassNotFound javax.ws.rs.core.UriBuilder not ...

Any ideas?

[jansupol]

I think I found it. jaxrs-ri bundle does not export javax.ws.rs. To do that:

• make jakarta.ws.rs provided rather than optional
• includeGroupIds should be jakarta.ws.rs

[jansupol]

@mkarg Please make this PR towards EE4J_8 branch

[mkarg]

Please make this PR towards EE4J_8 branch

@jansupol You mean including the proposed changed and then rebase ontop of EE4J_8?

[jansupol]

Yes please. We have many changes in EE4J_8 branch only, so we will merge the branch to master after 2.28 release. I plan to keep master buildable against maven central till then, so I'd actually close this PR. It's good it passes, though.

[mkarg]

@jansupol Travis passes. :-) I will rebase the PR ontop EE4J_8 now. Stay tuned.

[mkarg]

@jansupol See #3994.

[jansupol]

Closing this in favor of #3994.