You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@shardingsphere.apache.org by GitBox <gi...@apache.org> on 2020/07/06 11:07:17 UTC

[GitHub] [shardingsphere] laingke opened a new issue #6283: Define a maven bom jar to uniform version

laingke opened a new issue #6283:
URL: https://github.com/apache/shardingsphere/issues/6283


   ### Is your feature request related to a problem?
   #6282, It would be chaos when multiple shardingsphere jars have different version code in one project
   ### Describe the feature you would like.
   Define a maven bom jar to uniform version, just like spring-boot-starter-parent or spring-boot-dependencies


----------------------------------------------------------------
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:
users@infra.apache.org



[GitHub] [shardingsphere] laingke commented on issue #6283: Define a maven bom jar to uniform version

Posted by GitBox <gi...@apache.org>.
laingke commented on issue #6283:
URL: https://github.com/apache/shardingsphere/issues/6283#issuecomment-655274486


   @tristaZero 
   Before #6282 was solved, the document describe an example that may mislead developer to use sharding-orchestration-reg-zookeeper-curator(4.0.1) when using shardingphere(4.1.1).
   
   So this has led me to ask such a question:
   Is it exists a strong dependency relationship that all the shardingphere module are in one single same version? 
   
   If not, in future, when the project becomes bigger and bigger, It is better to define a parent dependency version requirement.
   
   


----------------------------------------------------------------
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:
users@infra.apache.org



[GitHub] [shardingsphere] tristaZero commented on issue #6283: Define a maven bom jar to uniform version

Posted by GitBox <gi...@apache.org>.
tristaZero commented on issue #6283:
URL: https://github.com/apache/shardingsphere/issues/6283#issuecomment-655868011


   @laingke 
   All the modules are supposed to keep in the same release version. If not, maybe it is a mistake. Welcome your feedback. :)


----------------------------------------------------------------
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:
users@infra.apache.org



[GitHub] [shardingsphere] tristaZero closed issue #6283: Define a maven bom jar to uniform version

Posted by GitBox <gi...@apache.org>.
tristaZero closed issue #6283:
URL: https://github.com/apache/shardingsphere/issues/6283


   


----------------------------------------------------------------
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:
users@infra.apache.org



[GitHub] [shardingsphere] tristaZero commented on issue #6283: Define a maven bom jar to uniform version

Posted by GitBox <gi...@apache.org>.
tristaZero commented on issue #6283:
URL: https://github.com/apache/shardingsphere/issues/6283#issuecomment-655238108


   @laingke 
   Hi, since #6282 has been closed, I will close this one alike.


----------------------------------------------------------------
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:
users@infra.apache.org