-
Notifications
You must be signed in to change notification settings - Fork 49
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
HBASE-25863 Shade javax.ws.rs package for use with shaded Jersey #51
HBASE-25863 Shade javax.ws.rs package for use with shaded Jersey #51
Conversation
Parking this here for now. Will be back with a PR vs. hbase-core that makes use of this, so we can verify it's all working the way we intend. |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Adapt to the changes provided by apache/hbase-thirdparty#51
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since the relocated jaxrs provider is intimately tied to our use of jersey, can we fold this into our packaged relocation of jersey in the hbase-shaded-jersey
module?
I chose intentionally not to do that, because we don't currently use this dependency in the |
Please put a comment to this end in the module pom |
fdd0a55
to
74b2d75
Compare
🎊 +1 overall
This message was automatically generated. |
74b2d75
to
48e61a5
Compare
Adapt to the changes provided by apache/hbase-thirdparty#51
🎊 +1 overall
This message was automatically generated. |
So any updates here? I plan to do a 4.0.0 release for hbase-thirdparty, so we can include this now? Thanks. |
@Apache9 There are two approvals here, I say just go ahead |
This PR is probably fine to merge. I'd wanted to land the dependent feature in HBase before committing here, but I've been pulled onto other projects and haven't gotten back to finishing it. |
48e61a5
to
fee9e85
Compare
… shaded Jersey From the [About](https://eclipse-ee4j.github.io/jersey/) text, > Jersey RESTful Web Services 2.x framework is open source, production quality, framework for > developing RESTful Web Services in Java that provides support for JAX-RS APIs and serves as a > JAX-RS (JSR 311 & JSR 339 & JSR 370) Reference Implementation. `javax.ws.rs` is defined by the JSRs, so it doesn't make sense that we could have multiple implementations of that JSR on the classpath simultaniously (via jersey-server-1.x and jersey-server-2.x jars) without them colliding. By shading over the JSR package space in the jersey-server-2.x implementation jars, we achieve a completely isolated JSR runtime. Signed-off-by: Sean Busbey <busbey@apache.org> Signed-off-by: Andrew Purtell <apurtell@apache.org>
…use with shaded jersey Make this provider module compatible with our shaded Jersey. Signed-off-by: Sean Busbey <busbey@apache.org> Signed-off-by: Andrew Purtell <apurtell@apache.org>
fee9e85
to
f902b25
Compare
Adapt to the changes provided by apache/hbase-thirdparty#51
Adapt to the changes provided by apache/hbase-thirdparty#51 Signed-off-by: Andrew Purtell <apurtell@apache.org>
Adapt to the changes provided by apache/hbase-thirdparty#51 Signed-off-by: Andrew Purtell <apurtell@apache.org>
From the About text,
javax.ws.rs
is defined by the JSRs, so it doesn't make sense that we could have multipleimplementations of that JSR on the classpath simultaniously (via jersey-server-1.x and
jersey-server-2.x jars) without them colliding. By shading over the JSR package space in the
jersey-server-2.x implementation jars, we achieve a completely isolated JSR runtime.