Dependency ranges cause other party builds to fail
Issue #396
resolved
We discussed it here briefly and it looks like a change was made, but the problem is back (this time it's bouncy castle dependencies that have ranges): https://bitbucket.org/connect2id/nimbus-jose-jwt/issues/283/dependency-failing-when-used-with-latest.
Comments (3)
-
-
Actually, now I look closer, I see that the Bouncy Castle dependencies are now marked as “optional”, so this is not an issue with the latest version (it was with an older one I was using).
-
- changed status to resolved
The BC 1.x is deliberately kept optional and as a range to let developers easily switch to a more recent (or some other) version without needing a new or special release of the Nimbus library.
BC is imported to allow its usage as an alt JCA provider.
Some utility classes also use it, and this use is clearly indicated.
- Log in to comment
(That was me BTW - didn’t realise I wasn’t logged in)