Open jackson-chris opened 5 years ago
When using:
<dependency> <groupId>net.wasdev.maven.tools.targets</groupId> <artifactId>liberty-target</artifactId> <version>19.0.0.4</version> <type>pom</type> <scope>provided</scope> </dependency>
We see that the following dependency is pulled in:
<dependency> <groupId>javax.ws.rs</groupId> <artifactId>javax.ws.rs-api</artifactId> <version>2.0</version> </dependency>
This is a transitive dependency from:
<dependency> <groupId>net.wasdev.maven.tools.targets</groupId> <artifactId>java-specs</artifactId> <version>1.0</version> </dependency>
I'm wondering why javax.ws.rs-api:2.0 is still being pulled in instead of javax.ws.rs-api:2.1, JAX-RS 2.1 has been supported since 18.0.0.2.
javax.ws.rs-api:2.0
javax.ws.rs-api:2.1
18.0.0.2
This is problematic for people developing JAX-RS 2.1 applications as certain annotations are not available.
When using:
We see that the following dependency is pulled in:
This is a transitive dependency from:
I'm wondering why
javax.ws.rs-api:2.0
is still being pulled in instead ofjavax.ws.rs-api:2.1
, JAX-RS 2.1 has been supported since18.0.0.2
.This is problematic for people developing JAX-RS 2.1 applications as certain annotations are not available.