-
Type: Bug
-
Resolution: Fixed
-
Priority: Minor - P4
-
Affects Version/s: 3.12.1
-
Component/s: Build, Client Side Encryption
-
None
-
Environment:Java with OSGi
This seems quite similar and/or an follow-up to JAVA-3575 that still exists as of version 3.12.1.
The manifest.xml of mongodb-driver-sync declares a required import of
com.mongodb.crypt.capi;version="[1.0,2)"
... which would be provided by mongodb-crypt
This is odd for multiple reasons
- Is mongodb-crypt required at all, even if not using any client side encryption?
- My unit-tests (not using osgi, so ignoring manifest.xml) seem to work without it and
JAVA-3575more or less hints that it should be optional.
- mongodb-driver-sync does not maven-depend on it (https://mvnrepository.com/artifact/org.mongodb/mongodb-driver-sync/3.12.1) at all.
- To some degree it was an optional dependency before
JAVA-3575via mongodb-driver-core. - Currently there is no maven dependency at all. So, without manual addition, it won't run in osgi.
- To some degree it was an optional dependency before
Probably
com.mongodb.crypt.capi;version="[1.0,2)"
should be declared optional?