I can pass based on branch-4.10, but I reported the following error in Tag v4.10.0-rc0
Used command: mvn clean install -DskipTests -Dstream -Dtwitter [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Total time: 01:46 min [INFO] Finished at: 2019-11-01T18:00:05+08:00 [INFO] ------------------------------------------------------------------------ [ERROR] Failed to execute goal on project twitter-science-provider: Could not resolve dependencies for project org.apache.bookkeeper.stats:twitter-science-provider:jar:4.10.0: The following artifacts could not be resolved: com.twitter.common:stats:jar:0.0.64, com.twitter.common:stat-registry:jar:0.0.10, com.twitter.common:stat:jar:0.0.11, com.twitter.common:stats-provider:jar:0.0.36, com.twitter.common:application-action:jar:0.0.44, com.twitter.common:net-util:jar:0.0.49, com.twitter.common:base:jar:0.0.57, com.twitter.common:util-system-mocks:jar:0.0.43, com.twitter.common:collections:jar:0.0.48, com.twitter.common:quantity:jar:0.0.44, com.twitter.common:util-sampler:jar:0.0.33, com.twitter.common:net-http-handlers:jar:0.0.39, com.twitter.common:net-http-handlers-text:jar:0.0.20, com.twitter.common:net-http-handlers-string-template:jar:0.0.26, com.twitter.common:util-templating:jar:0.0.2, com.twitter.common:stats-time-series:jar:0.0.36, com.twitter.common:stats-jvm:jar:0.0.33: Failure to find com.twitter.common:stats:jar:0.0.64 in https://maven.twttr.com was cached in the local repository, resolution will not be reattempted until the update interval of twitter has elapsed or updates are forced -> [Help 1] Yong Zhang <zhangyong1025...@gmail.com> 于2019年11月1日周五 下午1:26写道： > Hi Enrico, > > I verify the release candidate: > > - verify shasum of the source package and binary package > - using binary package to start a standalone service is good > - using the library to test the write and read are good > > But there are something wrong when I running standalone service after > building the source packages.I ‘m not sure if that problem is caused by > my operations. > > ``` > ➜ bookkeeper-4.10.0 mvn clean install -DskipTests -Dtwitter -Dstream > ➜ bookkeeper-4.10.0 bin/bookkeeper standalone > JAVA_HOME not set, using java from PATH. (/usr/bin/java) > the classpath of module 'stream/server' is not found, generating it ... > see output at > /Users/zhangyong/java/release-bookie/bookkeeper-4.10.0/stream/server/target/build_classpath.out > for the progress ... > the classpath of module 'stream/server' is generated at > '/Users/zhangyong/java/release-bookie/bookkeeper-4.10.0/stream/server/target/cached_classpath.txt'. > Error: Could not find or load main class > org.apache.bookkeeper.stream.cluster.StandaloneStarter > ➜ bookkeeper-4.10.0 bin/bookkeeper bookie > JAVA_HOME not set, using java from PATH. (/usr/bin/java) > the classpath of module 'bookkeeper-server' is not found, generating it ... > see output at > /Users/zhangyong/java/release-bookie/bookkeeper-4.10.0/bookkeeper-server/target/build_classpath.out > for the progress ... > the classpath of module 'bookkeeper-server' is generated at > '/Users/zhangyong/java/release-bookie/bookkeeper-4.10.0/bookkeeper-server/target/cached_classpath.txt'. > Error: Could not find or load main class org.apache.bookkeeper.server.Main > ``` > > Using binary package the standalone service starts well. And using the > master code to build it the service starts well too. When I checkout to > v4.10.0-rc0 and rebuild it, the same problem appears. > > > > Thanks, > Yong > > --- > > On Oct 31, 2019, at 7:46 PM, Enrico Olivelli <eolive...@gmail.com> > wrote: > > > > Hi everyone, > > Please review and vote on the release candidate #0 for the version > 4.10.0, > > as follows: > > [ ] +1, Approve the release > > [ ] -1, Do not approve the release (please provide specific comments) > > > > The complete staging area is available for your review, which includes: > > * Release notes [1] > > * The official Apache source and binary distributions to be deployed to > > dist.apache.org [2] > > * All artifacts to be deployed to the Maven Central Repository [3] > > * Source code tag "v4.10.0-rc0" [4] with git sha > > 2f08377f5c56f96389fb3a8e51844844537e118b > > > > BookKeeper's KEYS file contains PGP keys we used to sign this release: > > https://dist.apache.org/repos/dist/release/bookkeeper/KEYS > > > > Please download these packages and review this release candidate: > > > > - Review release notes > > - Download the source package (verify shasum, and asc) and follow the > > instructions to build and run the bookkeeper service. > > - Download the binary package (verify shasum, and asc) and follow the > > instructions to run the bookkeeper service. > > - Review maven repo, release tag, licenses, and any other things you > think > > it is important to a release. > > > > The vote will be open for at least 72 hours. It is adopted by majority > > approval, with at least 3 PMC affirmative votes. > > > > Thanks, > > Enrico Olivelli > > > > [1] > > > https://github.com/apache/bookkeeper/pull/2165/commits/0d91a95f306031d85c6a8195b0e6d73523cbfc0a > > [2] > https://dist.apache.org/repos/dist/dev/bookkeeper/bookkeeper-4.10.0-rc0/ > > [3] > > > https://repository.apache.org/content/repositories/orgapachebookkeeper-1043/ > > [4] https://github.com/apache/bookkeeper/tree/v4.10.0-rc0 > >
