blob: 35e6a785a94a58ccff238744c17c59d5f4e2f31c (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
|
# AutoValue Changes
## 1.1 → 1.2
### Functional changes
* A **provisional** extension API has been introduced. This **will change**
in a later release. If you want to use it regardless, see the
[AutoValueExtension] class.
* Properties of primitive array type (e.g. `byte[]`) are no longer cloned
when read. If your `@AutoValue` class includes an array property, by default
it will get a compiler warning, which can be suppressed with
`@SuppressWarnings("mutable")`.
* An `@AutoValue.Builder` type can now define both the setter and builder
methods like so:
```
...
abstract void setStrings(ImmutableList<String>);
abstract ImmutableList.Builder<String> stringsBuilder();
...
```
At runtime, if `stringsBuilder()...` is called then it is an error to call
`setStrings(...)` afterwards.
* The classes in the autovalue jar are now shaded with a `$` so they never
appear in IDE autocompletion.
* AutoValue now uses its own implementation of a subset of Apache Velocity,
so there will no longer be problems with interference between the Velocity
that was bundled with AutoValue and other versions that might be present.
### Bugs fixed
* Explicit check for nested `@AutoValue` classes being private, or not being
static. Otherwise the compiler errors could be hard to understand,
especially in IDEs.
* An Eclipse bug that could occasionally lead to exceptions in the IDE has
been fixed (GitHub issue #200).
* Fixed a bug where AutoValue generated incorrect code if a method with a
type parameter was inherited by a class that supplies a concrete type for
that parameter. For example `StringIterator implements Iterator<String>`,
where the type of `next()` is String, not `T`.
* In `AutoValueProcessor`, fixed an exception that happened if the same
abstract method was inherited from more than one parent (Github Issue #267).
* AutoValue now works correctly in an environment where
`@javax.annotation.Generated` does not exist.
* Properties marked `@Nullable` now get `@Nullable` on the corresponding
constructor parameters in the generated class.
## 1.0 → 1.1
### Functional changes
* Adds builders to AutoValue. Builders are nested classes annotated with
`@AutoValue.Builder`.
* Annotates constructor parameters with `@Nullable` if the corresponding
property methods are `@Nullable`.
* Changes Maven shading so org.apache.commons is shaded.
* Copies a `@GwtCompatible` annotation from the `@AutoValue` class to its
implementation subclass.
### Bugs fixed
* Works around a bug in the Eclipse compiler that meant that annotations
would be incorrectly copied from `@AutoValue` methods to their
implementations.
## 1.0 (Initial Release)
* Allows automatic generation of value type implementations
See [the AutoValue User's Guide](userguide/index.md)
[AutoValueExtension]: src/main/java/com/google/auto/value/extension/AutoValueExtension.java
|
