GitHub user funky-eyes added a comment to the discussion: How to Retain Used By After Migrating to an Apache Organization
 如图上图所示，将seata-compatible作为old package的存放点是可行的，但是作为seata-all去打包，反被apache seata依赖是不可行的，因为循环依赖的存在无法通过maven直接打包成功。 所以我觉得由于ioseata还是可以不改groupid去发，我当时想的结合方案 1.按照方案三，先通过compatible去解开新老package的管理，分离开，依赖关系只会有compatible依赖orgapacheseata，因为compatible只是接口 2.然后seata-all这个包发一个空包，内部没实现，只是用来统计used by，版本号可以起一个statistics，类似类似这样的标识，不代表正确版本 3.在org.apache.seata中引用这个统计用的seata-all As shown in the figure above, seata-compatible as the old package repository is feasible, but as seata-all to package, anti-apache seata dependency is not feasible, because of the existence of circular dependencies can not be packaged through the maven direct success. So I think because ioseata can still not change the groupid to send, I was thinking of combining the program 1. according to program three, first through compatible to unlock the management of the old and new package, separated from the dependencies will only have compatible dependency orgapacheseata, because compatible is just the interface 2. then seata-all this package to send an empty package, the internal did not realize, just used to statistics used by, the version number can be a statistics, similar to such a logo, does not represent the correct version 3. in the org.apache.seata reference to the statistics used by the seata-all GitHub link: https://github.com/apache/incubator-seata/discussions/6058#discussioncomment-8230522 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
