GitHub user funky-eyes edited a discussion: How to Retain Used By After Migrating to an Apache Organization
我有几个想法： 1. 发布apache-seata的包(该版本不做包名迁移,依旧保留io.seata的包,也就是发布一个seata-all的apache org的包)，发布一个io.seata:seata-all 1.9.0 内部无任何代码，只有maven依赖apache-seata-all的依赖包,并且去除shade io.seata的操作，这样只要有用户使用io.seata下的seata-all，就会引入org.apache.seata的依赖,随着时间,无论使用apacheseata还是io.seata的用户都会算到org.apache.seata:seata-all中. 该方案依旧会清空当前的usedby,但是如果用户用新版的io.seata就会引入apache-seata,这样用户无论是使用io.seata的最新版,还是apacheseata,二者均会记录到apacheseata:seata-all中,有助于快速提升apache seata的used by数量. 2. 发布一个io.seata下的seata，也是一样没有任何代码，被apache-seata所依赖，然后used by这块统计延续使用io.seata:seata-all即可,usedby会得到保留,因为无论使用io.seata还是apache.seata,最终都包含io.seata:seata-all 3. 新增一个seata-conversion模块内部包含io.seata:seata-all,将需要保留的api/注解/拦截器等都迁移到该模块中,最终打包为org.apache.seata:seata-all,该依赖包含org.apache.seata:seata-conversion该模块再引入io.seata:seata-all,这样用户使用org.apache.seata时,便依赖了io.seata,而io.seata中不再是个空包而是存储少量的api/注解/拦截器等需要向下兼容的类. used by改为 org.apache.seata:seata-all,此方案依旧会清空当前的usedby. 如果社区的各位有更多想法欢迎在此讨论  I have a few ideas: 1. Publish the apache-seata package (this version does not do package name migration, still retains the io.seata package, that is, publishes a seata-all apache org package), publishes an io.seata:seata-all 1.9.0 There is no code inside, only maven depends on apache-seata-all's dependency package, and the shade is removed io.seata, so that as long as a user uses seata-all under io.seata, the dependency of org.apache.seata will be introduced, and over time, users who use both apacheseata and io.seata will be counted in org.apache.seata:seata-all. This solution will still clear the current usedby, but if the user uses the new version of io.seata, apache-seata will be introduced, so that whether the user is using the latest version of io.seata or apacheseata, both will be recorded in apacheseata:seata-all, which helps to quickly increase the number of used by of apache seata. 2. Publish a seata under io.seata, which is also without any code, and is dependent on apache-seata, and then used by This statistic continues to use io.seata:seata-all, and usedby will be retained, because whether you use io.seata or apache.seata, it will eventually contain io.seata:seata-all 3. Add a seata-conversion module that contains io.seata:seata-all, migrate the api/annotation/interceptor that needs to be retained to this module, and finally package it as org.apache.seata:seata-all, the dependency contains org.apache.seata:seata-conversion, and then introduce io.seata: seata-all, so that when you use org.apache.seata, you are relying on io.seata, and io.seata is no longer an empty packet but stores a small number of APIs/annotations/interceptors and other classes that need to be backwards compatible. used by to org.apache.seata:seata-all, this solution will still clear the current usedby. If you have more ideas from the community, please feel free to discuss them here GitHub link: https://github.com/apache/incubator-seata/discussions/6058 ---- 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]
