Are some of those possibly something you could make optional? Dealing with old jars compile chains can be really enlightening in osgi :)
> On Jun 14, 2020, at 9:37 PM, Mark Derricutt <m...@talios.com> wrote: > > Hey all, > > I was wondering if anyone here had tried integrating/running OpenJSEE ( > https://github.com/openjsse/openjsse <https://github.com/openjsse/openjsse> ) > under Karaf on JDk8 at all? (we're wanting to make use of TLS 1.3 ). > > I've created a simple bundle wrapping the library, and calling > java.security.Security#insertProviderAt which we currently use on a non-Kara > based project, but when I try and build a distribution I rightly get told off > about the bundle wanting to access sun.net.util: > > resolution:=mandatory [caused by: Unable to resolve > com.smxemail.openjsse/1.0.1.SNAPSHOT: missing > requirement [com.smxemail.openjsse/1.0.1.SNAPSHOT] osgi.wiring.package; > filter:="(osgi.wiring.package=sun.net.util)"]] > Ideally I don't want to patch the jre.properties and export the sun.net.util > package (and likely others) so wondering if anyone had any ideas, one option > I'm thinking of trying is copying the openjsee.jar dependency into the > karaf/lib/boot folder, or set add the org.openjsse.net.ssl package to > delegate to the boot class loader. > > All of these feel somewhat messy, so if there was some way I could handle it > all inside a bundle/karaf-feature that would be preferable. > > Cheers, > Mark > > "The ease with which a change can be implemented has no relevance at all to > whether it is the right change for the (Java) Platform for all time." — Mark > Reinhold. > > Mark Derricutt > http://www.chaliceofblood.net <http://www.chaliceofblood.net/> > http://www.theoryinpractice.net <http://www.theoryinpractice.net/> > http://twitter.com/talios <http://twitter.com/talios> > http://facebook.com/mderricutt <http://facebook.com/mderricutt>
