Update to current RDF4J version, removing transitive vulnerability. #48
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.
Updating pom to rdf4j 4.3.8 (and current slf4j 2.0.9). With RDF4j 4.0, RDF4JException moved, updating references to new path: org.eclipse.rdf4j.common.exception.RDF4JException. Also commenting out invocations of initialize() on SailRepository as Repository class no longer has an exposed initialized method. A project using rdfbeans was getting transitive vulnerability warnings from maven central on release, arising from rdfbeans depending on rdf4j 2.2, which itself had a dependency on a library using CVE-2020-15250. Solution is to move to current rdf4j release, but between version 2 and version 4, rdf4j changed the API. This pull request updates the dependencies and addresses the (minor) changes in the rd4j API.