Driver version
12.2.0
JAVA/JVM version
17.0.6
Problem description
With change of issue #2042 a check for non-mandatory jdk.net.ExtendedSocketOptions was added.
This is done in a fail-safe way here, but the Class#forName call leads a mandatory Import-Package being created in the manifest on package jdk.net, which was probably not intended and can lead to issues in OSGi-environments not providing this package:
Unable to resolve com.microsoft.sqlserver.mssql-jdbc/12.2.0: missing requirement [com.microsoft.sqlserver.mssql-jdbc/12.2.0] osgi.wiring.package; filter:="(osgi.wiring.package=jdk.net)"
Expected behavior
Would expect the Import-Package being declared as optional to also deploy in an environment without the package being exported.
Driver version
12.2.0
JAVA/JVM version
17.0.6
Problem description
With change of issue #2042 a check for non-mandatory jdk.net.ExtendedSocketOptions was added.
This is done in a fail-safe way here, but the Class#forName call leads a mandatory Import-Package being created in the manifest on package
jdk.net, which was probably not intended and can lead to issues in OSGi-environments not providing this package:Unable to resolve com.microsoft.sqlserver.mssql-jdbc/12.2.0: missing requirement [com.microsoft.sqlserver.mssql-jdbc/12.2.0] osgi.wiring.package; filter:="(osgi.wiring.package=jdk.net)"Expected behavior
Would expect the Import-Package being declared as optional to also deploy in an environment without the package being exported.