Migrating opsgenie-swagger to Jersey 2.X

[tariq1890]

Hello,

We use the opsgenie sdk in our web application and we are currently facing issues with it as we have moved to jersey 2.x.

Having both jersey 1.x and 2.x in our classpath causes a lot of issues due to which we are unable to run our web application as of now.

Is there any plan to use the jersey 2.x libraries? I am happy to do the migration myself and send a pull request.

[alpgurtan]

Hi,

At the moment, we are using Jersey 1.x for supporting Java 1.6. Good news is we will stop supporting Java 1.6 in our next major release and can change it to another client/version. Definitely, It is in our roadmap but hard to give exact date for this release. It will take a some time (we are planning to introduce other REST API domains with this release), and forking this project with Jersey 2.x will be the quickest solution. Sorry about the inconvenience...

By the way, we will happy to hear your feedback/requests in our community page too. You can write your expectation and request in this page. It can help us to prioritise and determine where we are headed :)

[tariq1890]

Thanks for the response @alpgurtan ! We shall post any questions that we may have on the discussion board.

[dvayanu]

This issue is rather old, but did you move to jersey 2 in meantime? Or is there an alternative implementation?

[tjuchniewicz]

Due to old Jersey we can't use native images supported since 2.35. See: https://eclipse-ee4j.github.io/jersey.github.io/documentation/latest/graalvm-native-image.html