OpenStack4j v3.0.2 with javax.ws.rs-api 2.0.1 and resteasy

[ScottMaclure]

Apologies in advance - unsure how to raise/discuss an issue like this. Don't do much java coding.

My project already uses javax.ws.rs-api v2.0.1 implementation from Oracle:

<dependency>
    <groupId>javax.ws.rs</groupId>
    <artifactId>javax.ws.rs-api</artifactId>
    <version>2.0.1</version>
</dependency>

I recently added openstack4j v3.0.2 and I get the following error when Oracle's jar loads first, and I try to authenticate:

java.lang.AbstractMethodError: 
javax.ws.rs.core.UriBuilder.uri(Ljava/lang/String;)Ljavax/ws/rs/core/UriBuilder;

Seems there's a some-kind of signature mismatch with the UriBuilder returned from resteasy, and I get a NPE - around UriBuilder.fromUri(someUriString) in openstack4j\connectors\resteasy\HttpCommand.java

I got the project/code to work by excluding javax.ws.rs-api dep and rely on resteasy-jaxrs & jaxrs-api for the project's needs (seems to work so far for the rest of the project).

I guess I'm after recommendations on best practice here? Can OpenStack4j be updated to use a newer version of resteasy-jaxrs, which may be compatible with javax.ws.rs-api, and then I could exclude jaxrs-api?

Or is that the wrong approach here?

[vinodborole]

@ScottMaclure

jaxrs-api - This is the spec jar for Resteasy and support the spec for JAX-RS versions
javax.ws.rs-api - This the official spec jar for the JAX-RS 2.x line

resteasy latest version 3.x supports the JAX-RS 2.x spec so it is safe to exclude javax.ws.rs-api jar, we are using 3.x version in openstack4j

you can read more about this here - https://jax-rs-spec.java.net/

[ScottMaclure]

Thanks for that info - that's what I've gone with for now.

It's worth noting that OpenStack4j v3.0.2 is using resteasy v2.3.7.Final though?

No issues thus far in rest of the project.