Hi Dave, This is because gitcommit plugin in the maven profile. It assumes the working directory is a git repo. It can be skipped with " -Dmaven. *gitcommitid*.*skip*=true "
If you run "mvn clean install -DskipTests -Dmaven.gitcommitid.skip=true", it should be working. I am not sure if that is an issue for blocking a release, I would like to see what other people's opinions as well. Also is this the only issue are you seeing? I would appreciate if all reviewers can review the whole release candidate and point out the problems that he found. so I can fix them in the next release candidate. - Sijie On Fri, Jul 20, 2018 at 12:12 PM Dave Fisher <dave2w...@comcast.net> wrote: > Hi - > > I’m currently -1 as I get errors building from source in: > > [*INFO*] Apache Pulsar :: Protobuf shaded ................... *FAILURE* > [ 0.049 s] > > [*ERROR*] Failed to execute goal > pl.project13.maven:git-commit-id-plugin:2.2.4:revision *(git-info)* on > project protobuf-shaded: *.git directory is not found! Please specify a > valid [dotGitDirectory] in your pom.xml* -> *[Help 1]* > > Regards, > Dave > > On Jul 19, 2018, at 4:43 PM, Sijie Guo <si...@apache.org> wrote: > > This is the 5th release candidate for Apache Pulsar, version > 2.1.0-incubating. > > It introduces following main features: > > - Pulsar I/O: a serverless connector framework built on top of Pulsar > Functions. > - TieredStorage: offloads bookkeeper ledgers to a cold storage (like S3). > - Stateful Function: Pulsar Functions supports storing state back to > bookkeeper. > - Go Client: a Go client wrapping over existing cpp client. > - Avro and Protobuf schema are supported. > > Full list of changes and fixes are available: > > https://github.com/apache/incubator-pulsar/milestone/13?closed=1 > > *** Please download, test and vote on this release. This vote will stay > open > for at least 72 hours *** > > Note that we are voting upon the source (tag), binaries are provided for > convenience. > > Source and binary files: > > https://dist.apache.org/repos/dist/dev/incubator/pulsar/pulsar-2.1.0-incubating-candidate-5/ > > SHA-1 checksums: > > f0f6b6d7c48d119da36fc4fa1f934fd1f9ba8498 > ./apache-pulsar-2.1.0-incubating-bin.tar.gz > > b6a968249a7c5d21be89ece27895b862efda9a92 > ./apache-pulsar-2.1.0-incubating-src.tar.gz > > ddcf929eb18082ff2b9979507054453e8e803ed3 > ./apache-pulsar-io-connectors-2.1.0-incubating-bin.tar.gz > > > Maven staging repo: > https://repository.apache.org/content/repositories/orgapachepulsar-1025/ > > The tag to be voted upon: > v2.1.0-incubating-candidate-5 (75f79b77f55fbad351cb517e7f3b8ba4ab2dc177) > > https://github.com/apache/incubator-pulsar/releases/tag/v2.1.0-incubating-candidate-5 > > Pulsar's KEYS file containing PGP keys we use to sign the release: > https://dist.apache.org/repos/dist/release/incubator/pulsar/KEYS > > Please download the the source package, and follow the README to build > and run the Pulsar standalone service. > > A few notes for reviewing/voting 2.1.0 release: > > - Starting from this release, we are shipping RPM & DEB packages for pulsar > non-java clients. > - Starting from this release, we are shipping a binary distribution called > `apache-pulsar-io-connectors` > including all built-in connectors. Each connector is packaged with all > their dependencies and > a META-INF/DEPEDENCIES file with licensing information for > all dependencies. > - Since there are a lot of features introduced in 2.1, I put up an > instruction for people to validate release candidate > on different features: > > https://github.com/apache/incubator-pulsar/wiki/Release-Candidate-Validation > > >
