This release fixes issue #916 and ensures that builders' NestedCollection changes are applied to the collection immediately as mutation methods are called, no longer requiring application developers to call .and() to 'commit' or apply a change. For example, prior to this release, the following code did not apply changes:
JwtBuilder builder = Jwts.builder();
builder.audience().add("an-audience"); // no .and() call
builder.compact(); // would not keep 'an-audience'Now this code works as expected and all other NestedCollection instances like it apply changes immediately (e.g. when calling
.add(value)).
However, standard fluent builder chains are still recommended for readability when feasible, e.g.
Jwts.builder()
.audience().add("an-audience").and() // allows fluent chaining
.subject("Joe")
// etc...
.compact()These same notes are repeated in the CHANGELOG, and as always, project documentation is in the README.
Please allow 30 minutes from the time this announcement is published for the release to be available in Maven Central.