Released 12.10.0 with mandatory OSGi-imports rg. com.ibm.security.auth.module fail deployments

[MrEasy]

Hi,
Have no permission to reopen #2608 but release 12.10.0 now contains the described manifest entries, that are described in #2608 and lead to failed deployments in OSGi-environments.

Further more release note under https://github.com/microsoft/mssql-jdbc/releases/tag/v12.10.0 describes it as fixed as well.

This unfortunately is a regression for such environments. As fix seems to have been merged, wondering what makes it reappear.

Edit: found it:
This fix that came afterwards broke it again: 8a77b15

[machavan]

The change done in PR #2609 got reverted in PR #2614.

This PR #2636 to restore it back has been merged.

As a temporary workaround, users can manually edit the manifest file in the (12.10.0_ driver jar to make it osgi compliant

[MrEasy]

Thanks for the fast fix!

@ecki and me were thinking about providing a testcase for it due to the similar issues from past: link - based on pax-exam might however not fit well into your testing framework.
Would you generally be interested in that?

[machavan]

Hi @MrEasy,

We will be happy to explore the options to add coverage for OSGi. Not sure but maybe there could be a way to add pax-exam tests in JUnit tests.

[ecki]

I think it integrates in junit, but I need to see in which build phase it fits and so on, will keep you posted, (an simpler solution would be to assert the manifest as string)

[machavan]

Sure @ecki, if you would like to put up a unit test case for this with either approach, please feel free to do so, we will review and take it forward.