Understand Guava API stability and @Beta annotations
masterGuava uses the @Beta annotation to signal API stability:
@BetaAPIs: These are subject to change, modification, or removal at any time. If you are developing a library that will be used by others, avoid using@BetaAPIs unless you repackage them. It is strongly recommended to use the Guava Beta Checker to prevent accidental usage.- Non-
@BetaAPIs: These are guaranteed to remain binary-compatible for the indefinite future. This includes@DeprecatedAPIs that are not marked as@Beta.
Other important stability notes:
- Serialization: Serialized forms of ALL objects are subject to change. Do not persist them for long-term use.
- Security: Guava classes are not designed to protect against malicious callers; do not use them for communication between trusted and untrusted code.