Details
-
Improvement
-
Status: Resolved
-
Major
-
Resolution: Implemented
-
None
Description
Several dependencies are defined with properties for versions. This allows overriding the dependency's version for each build. Example:
<jersey2.version>2.34</jersey2.version> ... <groupId>org.glassfish.jersey.containers</groupId> <artifactId>jersey-container-servlet-core</artifactId> <version>${jersey2.version}</version> </dependency>
The goal of this task is to apply the pattern above to all dependencies where version is defined directly. Example:
<dependency> <groupId>javax.activation</groupId> <artifactId>activation</artifactId> <version>1.1.1</version> </dependency>
Make sure to look for such dependencies in all POM files, e.g. hadoop-ozone/recon, etc.. For non-root POMs, please add dependencies with property-based version definition in the root POM's dependencyManagement section. Non-root POMs can then omit the <version> tag.
Attachments
Issue Links
- links to