diff options
author | Otto Kekäläinen <otto@seravo.fi> | 2016-07-03 15:26:04 +0300 |
---|---|---|
committer | Otto Kekäläinen <otto@seravo.fi> | 2016-07-03 15:26:04 +0300 |
commit | 3808d091f86e079c8f3437f5cd66bd2c507cef8a (patch) | |
tree | 83e72f0b4fb9548251fdb0af74003e1523251226 /java/compatibility_tests | |
parent | cae3b0cbb689d0ed1e5da73942a5a9705f3411b0 (diff) | |
download | protobuf-3808d091f86e079c8f3437f5cd66bd2c507cef8a.tar.gz protobuf-3808d091f86e079c8f3437f5cd66bd2c507cef8a.tar.bz2 protobuf-3808d091f86e079c8f3437f5cd66bd2c507cef8a.zip |
Fix spelling in strings and comments
Diffstat (limited to 'java/compatibility_tests')
-rw-r--r-- | java/compatibility_tests/README.md | 4 | ||||
-rwxr-xr-x | java/compatibility_tests/v2.5.0/test.sh | 8 |
2 files changed, 6 insertions, 6 deletions
diff --git a/java/compatibility_tests/README.md b/java/compatibility_tests/README.md index 2465941e..72c6034c 100644 --- a/java/compatibility_tests/README.md +++ b/java/compatibility_tests/README.md @@ -5,7 +5,7 @@ previously released versions. ## Directory Layout -For each released protobuf version we are testing compatiblity with, there +For each released protobuf version we are testing compatibility with, there is a sub-directory with the following layout (take v2.5.0 as an example): * v2.5.0 @@ -47,4 +47,4 @@ For each version, the test script will test: * only upgrading more_protos to the new version and see whether everything builds/runs fine. Both source compatibility and -binary compatiblity will be tested. +binary compatibility will be tested. diff --git a/java/compatibility_tests/v2.5.0/test.sh b/java/compatibility_tests/v2.5.0/test.sh index 05503bb1..b7922b1a 100755 --- a/java/compatibility_tests/v2.5.0/test.sh +++ b/java/compatibility_tests/v2.5.0/test.sh @@ -11,7 +11,7 @@ TEST_VERSION=`grep "^ <version>.*</version>" pom.xml | sed "s| <version>\(.*\) # The old version of protobuf that we are testing compatibility against. This # is usually the same as TEST_VERSION (i.e., we use the tests extracted from -# that version to test compatibilty of the newest runtime against it), but it +# that version to test compatibility of the newest runtime against it), but it # is also possible to use this same test set to test the compatibiilty of the # latest version against other versions. case "$1" in @@ -40,7 +40,7 @@ esac # Extract the latest protobuf version number. VERSION_NUMBER=`grep "^ <version>.*</version>" ../../pom.xml | sed "s| <version>\(.*\)</version>|\1|"` -echo "Running compatibilty tests between $VERSION_NUMBER and $OLD_VERSION" +echo "Running compatibility tests between $VERSION_NUMBER and $OLD_VERSION" # Check protoc [ -f ../../../src/protoc ] || { @@ -55,7 +55,7 @@ echo "Running compatibilty tests between $VERSION_NUMBER and $OLD_VERSION" popd } -# Download old version source for the compatiblity test +# Download old version source for the compatibility test [ -d protobuf ] || { git clone https://github.com/google/protobuf.git cd protobuf @@ -92,7 +92,7 @@ mvn clean test \ # jar against the new runtime directly without recompile. # Collect all test dependencies in a single jar file (except for protobuf) to -# make it easier to run binary compatibilty test (where we will need to run +# make it easier to run binary compatibility test (where we will need to run # the jar files directly). cd deps mvn assembly:single |