NameDateSize

..02-Jul-20154 KiB

.classpath02-Jul-2015298

.gitignore02-Jul-20154

.project02-Jul-2015364

Android.mk02-Jul-20151 KiB

AUTHORS02-Jul-201552

build.gradle02-Jul-2015164

CleanSpec.mk02-Jul-20152.2 KiB

CONTRIBUTORS02-Jul-20159

COPYING02-Jul-201511.1 KiB

guava/02-Jul-20154 KiB

guava-bootstrap/02-Jul-20154 KiB

guava-gwt/02-Jul-20154 KiB

guava-testlib/02-Jul-20154 KiB

guava-tests/02-Jul-20154 KiB

MODULE_LICENSE_APACHE202-Jul-20150

mvn-deploy.sh02-Jul-20151.4 KiB

NOTICE02-Jul-201511.1 KiB

pom.xml02-Jul-20151.9 KiB

README02-Jul-20151.6 KiB

README.android02-Jul-2015540

README.maven02-Jul-20151.2 KiB

README

1Guava: Google Core Libraries for Java
2=====================================
3
4Requires JDK 1.5 or higher.
5
6Project page:
7  http://guava-libraries.googlecode.com
8
9Report a defect or feature request here:
10  http://code.google.com/p/guava-libraries/issues/entry
11
12Ask "how-to" and "why-didn't-it-work" questions at:
13  http://www.stackoverflow.com/questions/ask (use the "guava" tag)
14
15For open-ended questions and discussion:
16  http://groups.google.com/group/guava-discuss
17
18Subscribe to project updates in your feed reader:
19  http://code.google.com/feeds/p/guava-libraries/updates/basic
20
21IMPORTANT WARNINGS
22------------------
23
241. APIs marked with the @Beta annotation at the class or method level
25are subject to change. They can be modified in any way, or even
26removed, at any time. If your code is a library itself (i.e. it is
27used on the CLASSPATH of users outside your own control), you should
28not use beta APIs, unless you repackage them (e.g. using ProGuard).
29
302. Deprecated non-beta APIs will be removed eighteen months after the
31release in which they are first deprecated. You must fix your
32references before this time. If you don't, any manner of breakage
33could result (you are not guaranteed a compilation error).
34
353. Serialized forms of ALL objects are subject to change. Do not
36persist these and assume they can be read by a future version of the
37library.
38
394. Our classes are not designed to protect against a malicious caller.
40You should not use them for communication between trusted and
41untrusted code.
42
435. We unit-test and benchmark the libraries using only OpenJDK 1.6 on
44Linux. Some features, especially in com.google.common.io, may not work
45correctly in other environments.
46
47

README.android

1URL: http://code.google.com/p/guava-libraries/source/checkout
2Version: v11.0.2
3License: Apache 2
4Description: "Guava: Google Core Libraries for Java 1.5"
5
6Local Modifications: 
7   Commented out use of the non-public sun.misc.Unsafe
8   from guava/src/com/google/common/primitives/UnsignedBytes.java
9   Look for "BEGIN/END android-changed" markers.
10
11Guava-libraries are a grab bag of utility libraries published by Google as
12open source, including among other things the Google collections libraries.
13
14This code is built as a static library.
15

README.maven

1These folders host the maven metadata which are used to 
2build release binaries for hosting in the central maven 
3repositories.  These are not considered the "canonical" 
4build, but are maintained seperately by (a) volunteer(s) 
5with an interest in easy use of Guava by the Maven build 
6system.
7
8As a convenience, these folders have been set up to 
9provide alternate packaging of the sub-pmodules, which 
10correspond to their respective java packages, with 
11sources symbolically linked back to the main project.  
12This will work to allow command-line builds on MacOS X 
13or other Unix platforms which support symbolic linking, 
14but is not known to work on Windows platforms.  
15(Obviously the deployed binaries in maven repostories 
16will work fine on any compliant JVM).  
17
18The maintainers of these metadata have used M2Eclipse 
19to import these projects directly into Eclipse.  Please 
20remember that this codebase uses @Override annotations 
21on methods which implement an interface method, and 
22therefore require a JDK 1.6 (or newer 1.5 with the 
23appropriate fix) to support this behaviour.  Executing 
24Maven with an appropriate JAVA_HOME env is sufficient, 
25and these metadata do not have toolchain restrictions 
26currently set up.
27
28Christian
29cgruber@google.com
30