We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
At present, too many version configurations are introduced to control the component dependencies of spring-boot and spring-cloud. Such as:
<spring.eureka.version>2.2.1.RELEASE</spring.eureka.version> <spring.feign.version>2.2.1.RELEASE</spring.feign.version> <spring.boot.version>2.3.2.RELEASE</spring.boot.version> <spring.cloud.version>2.2.1.RELEASE</spring.cloud.version> <spring.version>5.2.15.RELEASE</spring.version> <spring.security.cryto.version>5.4.4</spring.security.cryto.version>
Use the following way:
<dependency> <groupId>org.springframework.boot</groupId> <artifactId>spring-boot-starter-parent</artifactId> <version>${spring.boot.version}</version> <type>pom</type> <scope>import</scope> </dependency> <dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-dependencies</artifactId> <version>${spring.cloud.version</version> <type>pom</type> <scope>import</scope> </dependency>
it provides a dependency-management section so that we can omit version tags for dependencies we are using in pom.xml
No response
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Search before asking
Problem Description
At present, too many version configurations are introduced to control the component dependencies of spring-boot and spring-cloud.
Such as:
Use the following way:
it provides a dependency-management section so that we can omit version tags for dependencies we are using in pom.xml
Description
No response
Use case
No response
solutions
No response
Anything else
No response
Are you willing to submit a PR?
The text was updated successfully, but these errors were encountered: