[MNG-6564] Lack of ability to overwrite properties of specified dependencies

• Type: New Feature
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 3.3.9
• Component/s: Dependencies
• Assignee: Unassigned
• Reporter: Rik Schaaf
• Created: 14/Jan/19 12:37
• Updated: 10/Dec/22 20:57

Description

For example, if I want to update the flyway version to 4.2.0 in spring boot 1.5 (by default Flyway 3.2.1) I want to do something like this: 

<properties>
  <flyway.version>4.2.0</flyway.version>
  <springboot.version>1.5.17.RELEASE</springboot.version>
</properties>

<dependencyManagement>
  <dependencies>
    <dependency>
      <groupId>org.springframework.boot</groupId>
      <artifactId>spring-boot-dependencies</artifactId>
      <version>${springboot.version}</version>
      <type>pom</type>
      <scope>import</scope>
    </dependency>
  <dependencies>
</dependencyManagement>

The flyway dependency is already defined in the dependency management of spring-boot-dependencies:

<dependency>
  <groupId>org.flywaydb</groupId>
  <artifactId>flyway-core</artifactId>
  <version>${flyway.version}</version>
</dependency>

But that same pom also defines flyway.version to be 3.2.1. When I include the flyway dependency in my own dependency management, my application does correctly use Flyway 4.2.0, but if I only provide the property, it incorrectly uses version 3.2.1, meaning that my property was ignored. I have heard from others that you can forcefully override a property by using a commandline parameter or an environment variable, but I would prefer to use a property in my pom file instead.

Issue Links

• is related to: MNG-7417 Several classes do not set properties properly for building requests
• relates to: MNG-5982 The POM for ... is invalid, transitive dependencies ... while property was overriden