ComparisonChain.compare(boolean, boolean) is too confusing, especially when
users have to negate or reverse the parameters so as to get true to come first.
Adding compareTrueFirst and compareFalseFirst, and deprecating compare(boolean,
boolean).
-------------
Created by MOE: http://code.google.com/p/moe-java
MOE_MIGRATED_REVID=28707952
Just reduce the default expectedValuesPerKey for HashMultimap from 8 to 2,
and for ArrayListMultimap from 10 to 3.

There's much more we could and should do but these one-character changes seem
like pure win to me.

http://code.google.com/p/guava-libraries/issues/detail?id=447
-------------
Created by MOE: http://code.google.com/p/moe-java
MOE_MIGRATED_REVID=28708533
Change Ascii.MIN and MAX from ints to chars.
-------------
Created by MOE: http://code.google.com/p/moe-java
MOE_MIGRATED_REVID=28708581
Expose ImmutableSortedMultiset
-------------
Created by MOE: http://code.google.com/p/moe-java
MOE_MIGRATED_REVID=28711726
Adds a ForwardingDeque.
-------------
Created by MOE: http://code.google.com/p/moe-java
MOE_MIGRATED_REVID=28714562
Remove unnecessary method type parameter.
-------------
Created by MOE: http://code.google.com/p/moe-java
MOE_MIGRATED_REVID=28715773
A few final minor javadoc fixes to close external guava bugs.
-------------
Created by MOE: http://code.google.com/p/moe-java
MOE_MIGRATED_REVID=28717009
Add private constructor (pointed out by Louis).
-------------
Created by MOE: http://code.google.com/p/moe-java
MOE_MIGRATED_REVID=28717208
Fix up deprecation messaging in ByteStreams and Files.
-------------
Created by MOE: http://code.google.com/p/moe-java
MOE_MIGRATED_REVID=28728118
specify missing version numbers
-------------
Created by MOE: http://code.google.com/p/moe-java
MOE_MIGRATED_REVID=28741770
Fix GWT behavior of "opportunistic" ImmutableList subclasses.
The "standard" ImmutableLists were fine, but Lists.charactersOf() and
TransformedImmutableList were broken.
Under Java, they inherited working implementations of their methods; under GWT,
they inherited versions that forwarded to an empty "delegate" collection.
I've overridden all forwarding methods in the GWT emulation in order to avoid
this.
I've also added tests for charactersOf(), which reveal that GWT
String/StringBuilder doesn't perform index checks, so I've added manual checks.
TransformedImmutableList could probably stand to have some tests, too, but at
least it will be exercised indirectly through the asList() views implemented
atop it in Louis's coming CL, which is in fact what revealed these problems.
-------------
Created by MOE: http://code.google.com/p/moe-java
MOE_MIGRATED_REVID=28741879
retract partition and partitionWithPadding from Guava
-------------
Created by MOE: http://code.google.com/p/moe-java
MOE_MIGRATED_REVID=28741930
Simplify ImmutableMultiset implementations.
From Louis: http://codereview.appspot.com/5780044/
-------------
Created by MOE: http://code.google.com/p/moe-java
MOE_MIGRATED_REVID=28742978
Stop erroneously placing the "normal Java" version of TestPlatform under guava-gwt.
(The GWT version happens to be missing, and we'll need to fix that up before the tests can run externally.)
This fixes the Guava build breakage introduced by my Collections2 CL.
Changed NullPointerTester to test inherited methods.

We only cover inherited methods from superclasses of the same package. This is
because we don't want to step into classes the author doesn't own.

For example, one may inherit from AbstractList, even though
AbstractList#equals() doesn't use @Nullable.

While for classes of the same package, we consider moving a method from subclass
to superclass a refactoring with no behavioral change. We don't want to silently
lose coverage just because of a "extract to superclass" refactoring.

Also, remove @GoogleInternal from getPackageName.
-------------
Created by MOE: http://code.google.com/p/moe-java
MOE_MIGRATED_REVID=28743194
Split SortedMap tests out of NavigableMap tests in preparation for running the former under GWT.
-------------
Created by MOE: http://code.google.com/p/moe-java
MOE_MIGRATED_REVID=28743199
Fix up erroneous git rebase?
-------------
Created by MOE: http://code.google.com/p/moe-java
MOE_MIGRATED_REVID=28743194
warn that Cache.asMap.get does _not_ automatically load values.
-------------
Created by MOE: http://code.google.com/p/moe-java
MOE_MIGRATED_REVID=28753957
Make KNOWN_ORDER significant for Map tests.
(There are no direct Map tests using KNOWN_ORDER, but we now pass KNOWN_ORDER on to our keySet, entrySet, and values sub-suites.)
Start using KNOWN_ORDER in various tests, including automatically in all SortedMap and SortedSet tests.
Introduce TestStringSortedMapGenerator to save us from having to write "sort(insertionOrder, Helpers.<String, String>entryComparator(Ordering.natural().nullsFirst()));" as an order() implementation over and over.
-------------
Created by MOE: http://code.google.com/p/moe-java
MOE_MIGRATED_REVID=28780249
Make MapTestSuiteBuilder (also BiMapTestSuiteBuilder) work under GWT, and then use it there (as well as the non-GWT ImmutableSortedMapTest, where it should have been used already).

This primarily involves making more derived suites (e.g., keySet(), values(), entrySet()) work under GWT.
The GWT test suites are produced with code generation, so, in order to work under GWT, a derived suite must be recognized by GwtTestSuiteGenerator so that we know how to generate code for it.
I've generalized the existing DerivedTestIteratorGenerator support to support any DerivedGenerator (each of which should have a one-arg constructor accepting its inner generator as an argument).

Now that we run MapTestSuiteBuilder tests, we can remove the individual, manually generated "derived" test suites.

The MapTestSuiteBuilder tests did encounter a couple problems:
- I had to move NullsBeforeB from MultisetCollectionTest to Helpers so that it could be used more widely (for reasons that its Javadoc hopefully makes clear).  (This was a problem in the test, not the production code.)
- I had to support null queries in the GWT ImmutableSortedMap.  (While I was there, I also prevented us from double-wrapping any submaps with unmodifiableSortedSet, since we know that the original map was already unmodifiable.  This is a tiny optimization.)  The null-query behavior was a "bug," albeit a very small one.

TODO(cpovirk): get the SortedMap tests running under GWT
-------------
Created by MOE: http://code.google.com/p/moe-java
MOE_MIGRATED_REVID=28784540