OSGi support basically means adding OSGI specific headers to MANIFEST.MF done automatically by maven-bundle-plugin from Apache Felix or bnd-maven-plugin from Bndtools, so that the driver could be loaded in OSGi environmental.
One thing I see as problematic is the dependency to Microsoft Azure Keyvault, which is also not OSGI compatible and their plans do not promise any good: Azure/azure-sdk-for-java#471. Transitive Microsoft dependencies also seem to be non-OSGi compatible. Apache HTTPClient dependency should be ok as the jar is OSGi ready, although the HTTP client dependency seems to be only because of Azure connections.
OSGi support basically means adding OSGI specific headers to MANIFEST.MF done automatically by maven-bundle-plugin from Apache Felix or bnd-maven-plugin from Bndtools, so that the driver could be loaded in OSGi environmental.
One thing I see as problematic is the dependency to Microsoft Azure Keyvault, which is also not OSGI compatible and their plans do not promise any good: Azure/azure-sdk-for-java#471. Transitive Microsoft dependencies also seem to be non-OSGi compatible. Apache HTTPClient dependency should be ok as the jar is OSGi ready, although the HTTP client dependency seems to be only because of Azure connections.