[WIP] Upgrade all runtime dependencies to the most recent version #2702
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The following remains and is left as is (I did a manual check that there was nothing better available) $ mvn versions:display-dependency-updates [INFO] com.google.code.findbugs:annotations ................ 3.0.1 -> 3.0.1u2 [INFO] com.powsybl:powsybl-build-tools ............................. 13 -> 14 [INFO] org.apache.groovy:groovy ..................... 4.0.14 -> 5.0.0-alpha-2 [INFO] org.apache.groovy:groovy-console ............. 4.0.14 -> 5.0.0-alpha-2 [INFO] org.apache.groovy:groovy-groovysh ............ 4.0.14 -> 5.0.0-alpha-2 [INFO] org.apache.groovy:groovy-nio ................. 4.0.14 -> 5.0.0-alpha-2 [INFO] org.apache.maven:maven-core ................... 3.8.5 -> 4.0.0-alpha-7 [INFO] org.eclipse.rdf4j:rdf4j-common-transaction ......... 4.3.6 -> 5.0.0-M1 [INFO] org.eclipse.rdf4j:rdf4j-repository-sail ............ 4.3.6 -> 5.0.0-M1 [INFO] org.eclipse.rdf4j:rdf4j-rio-rdfxml ................. 4.3.6 -> 5.0.0-M1 [INFO] org.eclipse.rdf4j:rdf4j-sail-memory ................ 4.3.6 -> 5.0.0-M1 TODO: there's at least one relocation I know of that I didn't handle: findbugs -> spotbugs TODO: are there other relocations ? Signed-off-by: HARPER Jon <jon.harper87@gmail.com>
|
Kudos, SonarCloud Quality Gate passed! |
geofjamg
changed the title
|
to be revisited when we know what to do with the univocity parsers |
|
Partially solved by #2704 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The following remains and is left as is (I did a manual check that there was nothing better available)
$ mvn versions:display-dependency-updates
[INFO] com.google.code.findbugs:annotations ................ 3.0.1 -> 3.0.1u2
[INFO] com.powsybl:powsybl-build-tools ............................. 13 -> 14
[INFO] org.apache.groovy:groovy ..................... 4.0.14 -> 5.0.0-alpha-2
[INFO] org.apache.groovy:groovy-console ............. 4.0.14 -> 5.0.0-alpha-2
[INFO] org.apache.groovy:groovy-groovysh ............ 4.0.14 -> 5.0.0-alpha-2
[INFO] org.apache.groovy:groovy-nio ................. 4.0.14 -> 5.0.0-alpha-2
[INFO] org.apache.maven:maven-core ................... 3.8.5 -> 4.0.0-alpha-7
[INFO] org.eclipse.rdf4j:rdf4j-common-transaction ......... 4.3.6 -> 5.0.0-M1
[INFO] org.eclipse.rdf4j:rdf4j-repository-sail ............ 4.3.6 -> 5.0.0-M1
[INFO] org.eclipse.rdf4j:rdf4j-rio-rdfxml ................. 4.3.6 -> 5.0.0-M1
[INFO] org.eclipse.rdf4j:rdf4j-sail-memory ................ 4.3.6 -> 5.0.0-M1
TODO: there's at least one relocation I know of that I didn't handle: findbugs -> spotbugs
TODO: are there other relocations ?
Please check if the PR fulfills these requirements
Does this PR already have an issue describing the problem?
NO
What kind of change does this PR introduce?
Feature
What is the current behavior?
Old deps
What is the new behavior (if this is a feature change)?
new deps !
Does this PR introduce a breaking change or deprecate an API?
Not sure, maybe worth mentionning
Other information:
based on code from #2124