aws-sdk-java-v2 icon indicating copy to clipboard operation
aws-sdk-java-v2 copied to clipboard

OSGI Bundle

Open shorea opened this issue 7 years ago • 6 comments

Make sure we play nice with the module systems in OSGI and Java9 (especially our detection of the default HTTP implementation). Ensure that we can provide modularized service clients to OSGI environments instead of a single uber jar containing the entire SDK.

shorea avatar Jul 11 '17 16:07 shorea

For Java 9 compatibility, at the very least please specify a stable "Automatic-Module-Name" in the jar manifests, and make sure there are no split packages across the different artifacts.

sindremehus avatar Nov 24 '17 13:11 sindremehus

We use DynamoDB SDK 1.x in a OSGi container and have to build our own bundle. Would be great if the new SDK would be OSGi compatible from the start.

jenslauterbach avatar Dec 15 '17 15:12 jenslauterbach

Any progress or info here? The split packages makes modularizing my app in Java 9+ effectively impossible.

bennyflint avatar Jun 06 '18 19:06 bennyflint

@bennyflint Yes, there's been a few PR's merged that hopefully address some of these issues:

  • #475
  • #480
  • #526

dagnir avatar Jun 27 '18 20:06 dagnir

#584

dagnir avatar Jun 27 '18 21:06 dagnir

What is going on with this issue, is there any progress into getting OSGi supported in clientbuilder code?

pegr69 avatar Sep 18 '22 19:09 pegr69

If split packages are no longer an issue (I sure hope so) then adding support for Java 9+ modules may still be done using the ModiTect plugin. This way the codebase remains Java 8 compatible. The build would have to jump to Java 11 at a minimum if it's not done so already.

aalmiray avatar Feb 20 '23 20:02 aalmiray