seregamorph opened a new issue, #13694:
URL: https://github.com/apache/maven/issues/13694
### New feature, improvement proposal
Consider the following:
```xml
<dependencyManagement>
<dependency>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-dependencies</artifactId>
<version>${spring-boot.version}</version>
<type>pom</type>
<scope>import</scope>
</dependency>
<dependency>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-starter-web</artifactId>
<!-- version is mandatory, while could be potentially omitted as we
know the version from spring-boot-dependencies -->
<version>${spring-boot.version}</version>
<exclusions>
<exclusion>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-starter-tomcat</artifactId>
</exclusion>
</exclusions>
</dependency>
...
```
We always have to declare the version, while in some scenarios this looks
redundant, e.g. when we just want to exclude a transitive dependency. Now we
have to extract a reused property (but this is even a good scenario when BOM
and a dependency from it are the same version).
The ultimate goal here is to allow more consistent versioning relying on a
single BOM without a risk to override a library dependency version (by mistake)
just because it's declared to exclude a transitive.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
