Upgrading dev.whyoleg.cryptography:cryptography-random 0.1 to 0.2
Breaking0.1.0 → 0.2.0Breaking3New3Changed1Other4
BreakingUpgrade verdict
3 breaking changes.
In plain terms
- The Maven artifact and package names for providers changed, so you must update your dependencies and imports.
- Creating a JDK provider is simpler: pass the security provider object or its name directly instead of wrapping it in JdkProvider.
- Some core classes and an annotation moved to a shorter package, so imports need updating.
Must act 3 items need code or config changes
What you must change
Breaking3
Renames provider artifacts and package names, e.g. cryptography-jdk becomes cryptography-provider-jdk.
cryptography-jdkcryptography-provider-jdkdev.whyoleg.cryptography.jdkdev.whyoleg.cryptography.providers.jdkRemoves JdkProvider and lets a java.security.Provider or its name be passed directly to CryptographyProvider.JDK.
JdkProviderCryptographyProvider.JDKjava.security.ProviderMoves several classes and an annotation to the dev.whyoleg.cryptography package.
CryptographyAlgorithmCryptographyAlgorithmNotFoundExceptionCryptographyProviderCryptographyProviderApiInsecureAlgorithm