[
https://issues.apache.org/jira/browse/JCLOUDS-1233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15851292#comment-15851292
]
Svetoslav Neykov commented on JCLOUDS-1233:
-------------------------------------------
Would be great if jclouds migrates to the current version of the JAX-RS spec.
Its usage of the API is limited so replacing the dependency is enough. That's
already been tested thoughroughly in the Apache Brooklyn project.
Another option is to go the guava way. In maven depend on the least common
denominator and in OSGi specify a version range. This will add another
dimension to the test matrices so not really worth it.
> Bump JAX-RS spec
> ----------------
>
> Key: JCLOUDS-1233
> URL: https://issues.apache.org/jira/browse/JCLOUDS-1233
> Project: jclouds
> Issue Type: Improvement
> Components: jclouds-core
> Affects Versions: 2.0.0
> Reporter: Andrea Turli
> Assignee: Andrea Turli
> Fix For: 2.0.1
>
>
> Looking at https://github.com/jclouds/jclouds/blob/master/core/pom.xml,
> jclouds-core uses:
> {code}
> <dependency>
> <groupId>javax.ws.rs</groupId>
> <artifactId>jsr311-api</artifactId>
> <version>1.1.1</version>
> </dependency>
> {code}
> which means that jclouds-core is using JAX-RS 1.x, while we may want to use
> {code}
> <dependency>
> <groupId>javax.ws.rs</groupId>
> <artifactId>javax.ws.rs-api</artifactId>
> <version>2.0.1</version>
> </dependency>
> {code}
> as javax.ws.rs-api is the official spec jar for the JAX-RS 2.x
> See
> http://stackoverflow.com/questions/32106428/jaxrs-api-vs-jsr311-api-vs-javax-ws-rs-api-vs-jersey-core
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
