Got it. that makes sense. I wonder if we could ping them to update the Maven repo now that Google itself has fixed the problem...
On Sun, Apr 7, 2013 at 1:17 PM, Henry Saputra (JIRA) <[email protected]>wrote: > > [ > https://issues.apache.org/jira/browse/TAJO-28?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13624970#comment-13624970] > > Henry Saputra edited comment on TAJO-28 at 4/7/13 5:15 PM: > ----------------------------------------------------------- > > Yeah, we should definitely bring the Apache Avro discussion in another > JIRA/thread =) > > As for protobuf issue, I did pass the issue patching the gtest with 1.5 > and mock the code in the protobuf a but to avoid exception. > > There is only one version of 2.4.1 in maven central: > http://search.maven.org/#search%7Cgav%7C1%7Cg%3A%22com.google.protobuf%22%20AND%20a%3A%22protobuf-java%22 > and last update is 06-Jul-2011 so probably wont have the gtest update. > I think they meant they update the gtest in the trunk which is the latest > 2.5.0 update. > > I think moving to 2.5.0 is better approach than dwelling with older > artifact. > > was (Author: hsaputra): > Yeah, we should definitely bring the Apache Avro discussion in another > JIRA/ thread =) > > As for protobuf issue, I did pass the issue patching the gtest with 1.5 > and mock the code in the protobuf a but to avoid exception. > > There is only one version of 2.4.1 in maven central: > http://search.maven.org/#search%7Cgav%7C1%7Cg%3A%22com.google.protobuf%22%20AND%20a%3A%22protobuf-java%22 > and last update is 06-Jul-2011 so probably wont have the gtest update. > > I think moving to 2.5.0 is better approach than dwelling with older > artifact. > > > Make Apache Tajo works with Protocol buffer 2.5.0 > > ------------------------------------------------- > > > > Key: TAJO-28 > > URL: https://issues.apache.org/jira/browse/TAJO-28 > > Project: Tajo > > Issue Type: Bug > > Components: rpc > > Reporter: Henry Saputra > > Assignee: Henry Saputra > > > > Early test indicates the code fail to compile with protocol buffer 2.5.0. > > Looks like we need to make it work with latest proto buffer version > (2.5.0) because of bug in gtest that prevent it to be install in some linux > versions: > > https://code.google.com/p/protobuf/issues/detail?id=433 > > -- > This message is automatically generated by JIRA. > If you think it was sent incorrectly, please contact your JIRA > administrators > For more information on JIRA, see: http://www.atlassian.com/software/jira >
