Upgrade dependencies #1241
Upgrade dependencies #1241
Conversation
Use a `dependencyManagement` for those projects which bring BOMs
build.gradle
Outdated
| @@ -15,10 +15,10 @@ plugins { | |||
| id 'project-report' | |||
| id 'idea' | |||
| id "org.sonarqube" version '2.7.1' | |||
| id 'org.asciidoctor.convert' version '1.6.1' | |||
| id "org.asciidoctor.convert" version '2.3.0' | |||
There was a problem hiding this comment.
why single to double here but double to single below?
There was a problem hiding this comment.
Copy/paste artefact: https://plugins.gradle.org/plugin/org.asciidoctor.convert
Although, I agree that I've changed the version template, but missed the name.
Shame on me.
Any other observation in this change?
Any objections at all?
I've just noticed that with BOM for JUnit we don't need to manage version for platform, as well as for Reactor Kafka.
If this is OK, I'll go ahead and fix similar way AMQP and SI
I don't see reason (yet) in managing all the dependency versiona in this section to avoid templating in the target sub-projects as it is done in SF: https://github.com/spring-projects/spring-framework/blob/master/build.gradle#L41
There was a problem hiding this comment.
No objections from me.
Use a
dependencyManagementfor those projects which bring BOMs