Hi, The original powered by page[1] has changed to users page[2]. [1] https://shardingsphere.apache.org/community/en/poweredby/ [2] https://shardingsphere.apache.org/community/en/users/ <https://shardingsphere.apache.org/community/en/poweredby/>
------------------ Liang Zhang (John) Apache ShardingSphere & Dubbo [email protected] <[email protected]> 于2020年3月4日周三 下午2:38写道： > I check the website https://jitpack.io, it looks like they[1] crawling > the releases from GitHub directly, and then shade the groupId and > artifactId by their own rule. > The repo `dangdangdotcom/sharding-jdbc` is the previous repo before > entering incubator, we just transferred the repo to > `apache/incubator-shardingsphere` now. > But jitpack may has a bug, they can not recognize the transferred repo. > > I check the release build log[1], the build is come from apache repo. > After building finish totally, shade the package name. Please see details > below: > > ``` > > [INFO] sharding-ui-distribution ........................... SUCCESS [ 0.690 > s] > [INFO] sharding-integration-test .......................... SUCCESS [ 0.145 > s] > [INFO] sharding-jdbc-test ................................. SUCCESS [ 0.527 > s] > [INFO] > ------------------------------------------------------------------------ > [INFO] BUILD SUCCESS > [INFO] > ------------------------------------------------------------------------ > [INFO] Total time: 05:06 min > [INFO] Finished at: 2019-12-27T07:30:17Z > [INFO] > ------------------------------------------------------------------------ > Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF-8 -Dhttps.protocols=TLSv1.2 > OpenJDK 64-Bit Server VM warning: ignoring option MaxPermSize=256m; support > was removed in 8.0 > Found module: org.apache.shardingsphere:shardingsphere:4.0.0 > ... > > Build tool exit code: 0 > Looking for artifacts... > Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF-8 -Dhttps.protocols=TLSv1.2 > Looking for pom.xml in build directory and ~/.m2 > Found artifact: org.apache.shardingsphere:shardingsphere:4.0.0 > 2019-12-27T07:30:34.790832592Z > Exit code: 0 > > Build artifacts: > com.github.dangdangdotcom.sharding-jdbc:sharding-proxy-distribution:4.0.0 > com.github.dangdangdotcom.sharding-jdbc:shardingsphere-sql-parser-sqlserver:4.0.0 > com.github.dangdangdotcom.sharding-jdbc:sharding-orchestration-reg-nacos:4.0.0 > ... > > ``` > > Could we just leave them there, any advice? > > [1] https://jitpack.io/p/dangdangdotcom/sharding-jdbc > [2] > https://jitpack.io/com/github/dangdangdotcom/sharding-jdbc/4.0.0/build.log > ------------------ > > Liang Zhang (John) > Apache ShardingSphere & Dubbo > > > Juan Pan <[email protected]> 于2020年3月4日周三 下午1:29写道： > >> Hi Justin, >> >> >> Thanks for your prompt feedback, which always provides us valuable >> instructions. >> It seems like items currently remaining Errata is not a big issue, and >> the more critical case is the brand thing. Besides, to make the website >> more 'Apache' is another improvement. Make sense, and we will look into >> two of them. >> >> >> Best wishes, >> Trista >> >> >> Juan Pan (Trista) >> >> Senior DBA & PPMC of Apache ShardingSphere(Incubating) >> E-mail: [email protected] >> >> >> >> >> On 03/4/2020 12:18，Justin Mclean<[email protected]> wrote： >> Hi, >> >> IMO it's not immediately obvious from the project web site that this is >> an Apache project. It probably meets the minimum requirements but it would >> be nice to see more than that. >> >> Thanks, >> Justin >> >
