cnhaicao commented on issue #1523: dubbo多分支api依赖版本管理问题
   Dubbo multi-branch api dependent version management issues
   According to the official recommendation, the public api project is 
extracted between the service provider and the service consumer. Both the 
service consumer and the service provider rely on this api project. When the 
dubbo-based microservice architecture is used, services are inevitably invoked. 
The problem that arises is that engineering depends on multiple api projects. 
We use jenkins to use all the api poll scm detection code changes when the API 
is automatically packaged to the internal network nexus PW.
   All service providers and consumers can rely on these api projects. When 
teams work together, it is inevitable to pull multiple branches for parallel 
development. At this point how to do API version dependency management?
   Assuming that there are branch api and rel two branches of the api may be 
modified, this time if the dev and rel branch api version number should not be 
distinguished, two branch api set a different version number, then dev / rel 
are Setting the poll scm to auto-negotiate nexus will inevitably lead to manual 
maintenance of the version number when the code is merged. Is there any other 
better way?

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:

With regards,
Apache Git Services

Reply via email to