MidnightFiend opened a new issue #7917:
URL: https://github.com/apache/shardingsphere/issues/7917


   ## Question
   when i create new product with 
   ```
   <!-- 
https://mvnrepository.com/artifact/org.apache.shardingsphere/sharding-jdbc-core 
-->
   <dependency>
       <groupId>org.apache.shardingsphere</groupId>
       <artifactId>sharding-jdbc-namespace</artifactId>
       <version>4.1.1</version>
   </dependency>
   ```
   
   at the same time, our company require to use openjdk11, so i should use 
spring version >5.1.x
   
   i use dependency 
   ```
   <dependency>
       <groupId>org.springframework.boot</groupId>
       <artifactId>spring-boot-dependencies</artifactId>
       <version>2.2.10-RELEASE</version>
       <type>pom</type>
       <scope>import</scope>
   </dependency>
   
   <dependency>
       <groupId>org.springframework.boot</groupId>
       <artifactId>spring-boot-starter</artifactId>
   </dependency>
   ```
   
   it dependency springframework version 5.2.9
   
   when i mvn package the project, i found mvn dependency:tree 
   [INFO] +- 
org.springframework.boot:spring-boot-starter:jar:2.2.10.RELEASE:compile
   [INFO] |  +- org.springframework.boot:spring-boot:jar:2.2.10.RELEASE:compile
   [INFO] |  |  \- org.springframework:spring-context:jar:4.3.16.RELEASE:compile
   [INFO] |  |     +- org.springframework:spring-aop:jar:4.3.16.RELEASE:compile
   [INFO] |  |     +- 
org.springframework:spring-beans:jar:4.3.16.RELEASE:compile
   
   i had traced which one import 4.3.16 , then i found in 
shardingsphere-4.1.1-pom :
   <springframework.version>[4.3.6.RELEASE,5.0.0.M1)</springframework.version>
   
   it may control springframework version less than 5.x.
   
   is there any way, i can skip it?
   
   
   


----------------------------------------------------------------
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.

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to