Upgrading bouncycastle and including javax.mail as a dependency #207
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There were runtime errors that occured during a large ingest for a missing field
sphincsPlus_shake_256
.Bumping bouncycastle to 1.71 solved this (bumping to latest version 1.79 didn't work as it does not have the field).
We previously expected
angus-mail
(as an implementation of jakartamail) (see Move from JavaMail to JakartaMail #131) to work as a drop-in replacement forjavax.mail
but there still seems to be a dependency onjavax.mail
, so we've added it. Not including it resulted inNoClassDefFoundError: javax/mail/Part
Testing
Tested on a local instance