I commit the PR to master but didn't see this error stack. As long as the latest slf4j-log4 binding jar is earlier in the class path the exception should not occur. Looks like it is not blocking but I ask Viacheslav Dobromyslov to verify when did he see it.
- Henry On Wed, Sep 17, 2014 at 9:33 AM, Henry Saputra <henry.sapu...@gmail.com> wrote: > We may have blocker with GORA-372: slf4j-api version conflict for Gora HBase > > - Henry > > On Tue, Sep 16, 2014 at 8:00 AM, Lewis John Mcgibbney > <lewis.mcgibb...@gmail.com> wrote: >> Hi Folks, >> I am very happy to get a VOTE out for Apache Gora 0.5 Release Candidate. >> >> We solved 44 issues: http://s.apache.org/0.5report >> >> Git source tag (c2d58dd1440b4e2c66c1f40a4b6d4169d79bb6d3): >> http://s.apache.org/Eyv >> >> Staging repo: >> https://repository.apache.org/content/repositories/orgapachegora-1001 >> >> Source Release Artifacts: https://dist.apache.org/repos/dist/dev/gora/0.5/ >> >> PGP release keys (signed using 48BAEBF6): http://gora.apache.org/dist/KEYS >> >> Vote will be open for 72 hours. >> Thank you to everyone that is able to VOTE as well as everyone that >> contributed to Apache Gora 0.5. >> >> [ ] +1, let's get it released!!! >> [ ] +/-0, fine, but consider to fix few issues before... >> [ ] -1, nope, because... (and please explain why) >> >> -- >> Lewis
