1. Added C++ tests under the release docker image.
2. Cleaned up tests.sh and removed traivis stuff.

1. Added C++ tests under the release docker image.
2. Fixed a compile issue with the docker image.
3. Cleaned up tests.sh and removed traivis stuff.

Add googletest as a submodule in third_party/googletest.

Fix the bug in following scenario:  

gmock is downloaded successfully while gtest not. Resuming "autogen.sh",
the gtest won't be downloaded. And following error will occur:  

$ ./autogen.sh
+ autoreconf -f -i -Wall,no-obsolete
aclocal: error: configure.ac:1: file 'gtest/m4/acx_pthread.m4' does not exist
autoreconf: aclocal failed with exit status: 1

The original link is no longer available.

Change-Id: I2976d3f19c8e818689549fb31ff20af8eae92a07

The original link is no longer available.

Change-Id: I2976d3f19c8e818689549fb31ff20af8eae92a07

Support curl -s argument.
Signed-off-by: Matthew Valimaki <matthew.valimaki@gmail.com>

[ci skip]

Change-Id: I9391c09640e0b0b2b21c45a97a1fc91814d95c5d

system. The Ruby module build now uses an amalgamated distribution of
upb, and successfully builds a Ruby gem called 'google-protobuf' with
module 'google/protobuf'.

This adds a Ruby extension in ruby/ that is based on the 'upb' library
(now included as a submodule), and adds support for Ruby code generation
to the protoc compiler.

nested autoconf package rather than as raw source.  This way we can
trivially update it again in the future.

Actually, this change doesn't even include gtest in protobuf's SVN.
Instead, we auto-download it when autogen.sh is invoked.  Note that
it will be included in release distributions, though.

TODO:
* Add a configure option to use the system's installed gtest rather
  than the bundled copy.  Apparently the gtest maintainers are working
  on some general-purpose autoconf macros which will do this
  automagically.
* Update MSVC project files.

committer: Jon Skeet <skeet@pobox.com>