[
https://issues.apache.org/jira/browse/HDDS-7371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Attila Doroszlai updated HDDS-7371:
-----------------------------------
Description:
Several dependencies are defined with properties for versions. This allows
overriding the dependency's version for each build. Example:
{code}
<jersey2.version>2.34</jersey2.version>
...
<groupId>org.glassfish.jersey.containers</groupId>
<artifactId>jersey-container-servlet-core</artifactId>
<version>${jersey2.version}</version>
</dependency>
{code}
The goal of this task is to apply the pattern above to all dependencies where
version is defined directly. Example:
{code}
<dependency>
<groupId>javax.activation</groupId>
<artifactId>activation</artifactId>
<version>1.1.1</version>
</dependency>
{code}
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|https://github.com/apache/ozone/blob/f9b74a25cffe77d4b8031fe332fe247b9bd596c8/pom.xml#L260].
Non-root POMs can then omit the {{<version>}} tag.
was:
Several dependencies are defined with properties for versions. This allows
overriding the dependency's version for each build. Example:
{code}
<jersey2.version>2.34</jersey2.version>
...
<groupId>org.glassfish.jersey.containers</groupId>
<artifactId>jersey-container-servlet-core</artifactId>
<version>${jersey2.version}</version>
</dependency>
{code}
The goal of this task is to apply the pattern above to all dependencies where
version is defined directly. Example:
{code}
<dependency>
<groupId>javax.activation</groupId>
<artifactId>activation</artifactId>
<version>1.1.1</version>
</dependency>
{code}
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|https://github.com/apache/ozone/blob/f9b74a25cffe77d4b8031fe332fe247b9bd596c8/pom.xml#L260].
Non-root POMs can then omit the {{<version>}} tag.
> Create properties for all dependency versions
> ---------------------------------------------
>
> Key: HDDS-7371
> URL: https://issues.apache.org/jira/browse/HDDS-7371
> Project: Apache Ozone
> Issue Type: Improvement
> Components: build
> Reporter: Attila Doroszlai
> Assignee: Rohit Kumar Badeau
> Priority: Major
>
> Several dependencies are defined with properties for versions. This allows
> overriding the dependency's version for each build. Example:
> {code}
> <jersey2.version>2.34</jersey2.version>
> ...
> <groupId>org.glassfish.jersey.containers</groupId>
> <artifactId>jersey-container-servlet-core</artifactId>
> <version>${jersey2.version}</version>
> </dependency>
> {code}
> The goal of this task is to apply the pattern above to all dependencies where
> version is defined directly. Example:
> {code}
> <dependency>
> <groupId>javax.activation</groupId>
> <artifactId>activation</artifactId>
> <version>1.1.1</version>
> </dependency>
> {code}
> 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|https://github.com/apache/ozone/blob/f9b74a25cffe77d4b8031fe332fe247b9bd596c8/pom.xml#L260].
> Non-root POMs can then omit the {{<version>}} tag.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
