-
Notifications
You must be signed in to change notification settings - Fork 2.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Jersey-common 2.13 - javax.ws.rs-api 2.0.1 and swagger-play2 1.3.12 incompatibility #900
Comments
Have you tried excluding the offending dependency from the swagger-core library that you use? |
I thought of that but I haven't tried it. I will ASAP and let you guys know
|
Ok, so, good news: I bumped everything to 1.3.13-SNAPSHOT (in second thought I should have bumped it to something like 1.3.12-RS2-SNAPSHOT, as it's a bit of a bummer to do so because one has to go through all the poms to do that. I think the version can be a property stated in the parent pom [I think this is doable, i'm not sure anymore], also, if I recall I also think that there was a maven plugin to assist with the version bumping, I haven't used mvn in a bit..) And all of the dependencies that one had with I'm glad to submit a pull request if you think this is worthy of that (while updating also the Readme.md to have this special note of a version with play2 support and rs-api 2.X) |
@fehguy: yet in another note (I write it here because I'm not sure if its related with this change or not) the |
Hi, that's intentional, there is a filter that requires a valid api key to show all validations. |
Didn't noticed that. Got it, the 'special-key' :) Nice, it actually works well with the version bumps I did, so nevermind my Tks for making it clearer to me, Tony. Cheers On Sat, Mar 14, 2015 at 4:12 PM, Tony Tam notifications@github.com wrote:
João Antunes |
Sure thing :) You're not the first person to miss that, I need to make it more clear. |
Closing as we're not going to release 1.3.13. Please upgrade to the latest version. |
Apologies, noticed this is related to the Play module and not the Jersey one. Please follow #918 for progress regarding the Play module migration. |
Hi Fellas!
Thanks for the great work.
I searched on the issues page for a solution for the problem that I have, the closest I found was this: #862 but I don't think I can just switch to 1.5.X-M because that branch only supports Jersey and not Play2.
So, I think that my problem is related with the following:
I have a play2-java 2.3.X (2.3.8) application, that also has a dependency with a library that uses javax.ws.rs-api 2.0.1 (https://github.com/paymill/paymill-java in its 5.0.0 version) and because swagger-play2 1.3.12 depends on an earlier version of the javax.ws.rs-api I get exceptions like these, when using Paymill's library:
Any thoughts on this? I kinda envy Node.js because of the way they deal with dependencies, when will Java support this..
The text was updated successfully, but these errors were encountered: