Default path for ssl key store is nested inside "JabRef" directory #8796
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.
While discussing #8791, it was sawn, that there is a two-level nesting of application data:
Selected examples:
Full path
For JabRef, it currently looks as follows:
Interpretation: The ssl trust store is stored one level too high. This PR fixes i. This PR is a follow-up to #8583.
Result:
CHANGELOG.md
described in a way that is understandable for the average user (if applicable)