Closed bmarwell closed 1 year ago
As a lazy developer, I do not want to define ${project.version} for reactor artifacts in each pom file again and again. Instead, I will define all modules and versions in my dependencyManagement of the reactor project's root pom like so:
<dependencyManagement> <dependency> <groupId>reactor.group.id</groupId> <artifactId>moduleA</artifactId> <version>${project.version}</version> </dependency> </dependencyManagement>
Those dependencies from the reactor will be left as-is.
This plugin will pick those managed dependencies up and try to downgrade them to the latest version available in the release repository.
Scenario prerequisites
Story
As a lazy developer, I do not want to define ${project.version} for reactor artifacts in each pom file again and again. Instead, I will define all modules and versions in my dependencyManagement of the reactor project's root pom like so:
Expected behaviour
Those dependencies from the reactor will be left as-is.
Actual behaviour
This plugin will pick those managed dependencies up and try to downgrade them to the latest version available in the release repository.