Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bump auto-value-annotations from 1.7 to 1.7.4 in /factory #901

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Oct 22, 2020

Bumps auto-value-annotations from 1.7 to 1.7.4.

Release notes

Sourced from auto-value-annotations's releases.

AutoValue 1.7.4

  • Stop the LazyInit annotation from getting shaded by Maven, so that AutoValue can find it on the classpath. (b484417)
  • Fixed handling of @Nullable Optional<T> foo() properties being set by setFoo(@Nullable T) setters. Now setFoo(null) results in Optional.empty(), not null. (d9d66ad)

AutoValue 1.7.3

  • Optionally copy annotations from the @AutoValue.Builder class to the generated subclass. (b22f969)
  • Drop unnecessary parentheses in AutoAnnotation equals and hashCode methods. (b9ba06a)
  • Fixed a problem when an @AutoValue class references types that are generated by other annotation processors. (2797d38)

AutoValue 1.7.2

Only one change in this release:

  • AutoValue is once again "isolating" for Gradle incremental compilation. (8e7515a)

AutoValue 1.7.1

New features

  • SerializableAutoValue extension. This can be used to serialize @AutoValue classes with properties of type java.util.Optional, even though java.util.Optional is not serializable, and it can also be configured to serialize other arbitrary types. Thanks to @alvinlao for this contribution! (f91d2fe)
  • The logic for determining if we can make a BarBuilder out of a Bar has been generalized. For example, if your @AutoValue class Foo has a property IntList ints(), then your builder can have IntListBuilder intsBuilder(). Previously this worked if there was no Foo.toBuilder() method, or if IntList had its own toBuilder() method. Now it also works if it is possible to call IntListBuilder.addAll(IntList). (6aeb44f)
  • AutoValue now allows boxed properties to be set from the corresponding primitive type, for example Integer from int. (2bbe506)

Behaviour changes

  • AutoValue now gives a warning if the static builder() method is inside the @AutoValue.Builder class instead of directly in the @AutoValue class. (fcccded)
  • AutoValue doesn't generate code or invoke extensions if it detects a problem, for example a mismatch between getters and setters. (ecb6032)
  • AutoOneOf factory methods for void values now have type parameters if the @AutoOneOf class does. (4ab1b53)
  • It is now a compilation error if a setter method in a builder has a parameter marked @Nullable when the corresponding property is not in fact @Nullable. Calling such a method with a null parameter already generated a NullPointerException at runtime. (bd7bed2)
  • The @Memoized annotation now has class-level retention, rather than source-level. (107694b)

Bug fixes

  • We fixed an issue with type checking of setter parameters in the presence of inheritance and generics. (e97d1f0)
  • We now generate a better toString() for arrays in AutoOneOf (0a7c049)

Miscellaneous

  • We added CompileWithEclipseTest, which checks that AutoValue works with ecj, the Eclipse compiler. (05e983c)
Commits
  • c59110e Set version number for auto-value-parent to 1.7.4.
  • b484417 Stop the LazyInit annotation from getting shaded by Maven, so that AutoValue ...
  • d9d66ad Fix handling of @Nullable Optional\<T> foo() properties being set by `setFoo...
  • da84ef1 Tests related to e62e0ab
  • df5641b [ #HiltMigration ] Updating BasicAnnotationProcessor to support a String-base...
  • e62e0ab Fix a problem with references to Factory classes in other packages.
  • 08f930a Make the nested @AutoValue class static otherwise you get the following error:
  • 32fdb09 Change links from google.github.io/guava to guava.dev, including making sure ...
  • 2f437b5 Change error reporting methods to use format strings.
  • b22f969 Copy annotations from @AutoValue.Builder to the generated Builder subclass.
  • Additional commits viewable in compare view

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps [auto-value-annotations](https://github.com/google/auto) from 1.7 to 1.7.4.
- [Release notes](https://github.com/google/auto/releases)
- [Commits](auto-value-1.7...auto-value-1.7.4)

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot added dependencies Pull requests that update a dependency file java Pull requests that update Java code labels Oct 22, 2020
@google-cla google-cla bot added the cla: yes label Oct 22, 2020
copybara-service bot pushed a commit that referenced this pull request Oct 22, 2020
Process:
  ( for F in common factory service value; do ( mvn org.codehaus.mojo:versions-maven-plugin:2.8.1:update-properties org.codehaus.mojo:versions-maven-plugin:2.8.1:use-latest-releases -f $F/pom.xml ); done && mvn org.codehaus.mojo:versions-maven-plugin:2.8.1:use-latest-versions -f value/src/it/gwtserializer/pom.xml )
  Then undid the Compile-Testing update in value/pom.xml. It somehow breaks things.
  And I undid the google-java-format update in factory/pom.xml. It isn't compatible with JDK8/9, which is what Travis is set up for. (And then I flailed around for 15 minutes because Maven didn't rebuild some files when I changed JDKs, producing mystery failures. Argh. Perhaps we should set `<useIncrementalCompilation>` to `false` everywhere.)
  (Someday I will remember -DgenerateBackupPoms=false....)

For some reason, gwtserializer responds to use-latest-versions but not to use-latest-releases, even though it's updating GWT to a release (just as in one of the other POMs).

We don't use use-latest-versions everywhere not just because it could theoretically pick a non-release versions but also because use-latest-versions replaces variable usages like ${guava-version} by inlining the value into them: mojohaus/versions#243

I would have updated the plugins in addition to the deps, but oddly the plugin does not support this: https://stackoverflow.com/q/34032262/28465

Fixes #919, #918, #917, #915, #914, #911, #908, #906, #904, #903, #901, #900, #899

RELNOTES=n/a
PiperOrigin-RevId: 338485304
copybara-service bot pushed a commit that referenced this pull request Oct 22, 2020
Process:
  ( for F in common factory service value; do ( mvn org.codehaus.mojo:versions-maven-plugin:2.8.1:update-properties org.codehaus.mojo:versions-maven-plugin:2.8.1:use-latest-releases -f $F/pom.xml ); done && mvn org.codehaus.mojo:versions-maven-plugin:2.8.1:use-latest-versions -f value/src/it/gwtserializer/pom.xml )
  Then undid the Compile-Testing update in value/pom.xml. It somehow breaks things.
  And I undid the google-java-format update in factory/pom.xml. It isn't compatible with JDK8/9, which is what Travis is set up for. (And then I flailed around for 15 minutes because Maven didn't rebuild some files when I changed JDKs, producing mystery failures. Argh. Perhaps we should set `<useIncrementalCompilation>` to `false` everywhere.)
  And *then* I undid the auto-service upgrade in value/processor/pom.xml. It causes problems but only under JDK9: https://travis-ci.org/github/google/auto/jobs/738096563 The error isn't in generated code, so I suspect a compiler bug. (But my quick search didn't find a filed OpenJDK issue.)
  (Someday I will remember -DgenerateBackupPoms=false....)

For some reason, gwtserializer responds to use-latest-versions but not to use-latest-releases, even though it's updating GWT to a release (just as in one of the other POMs).

We don't use use-latest-versions everywhere not just because it could theoretically pick a non-release versions but also because use-latest-versions replaces variable usages like ${guava-version} by inlining the value into them: mojohaus/versions#243

I would have updated the plugins in addition to the deps, but oddly the plugin does not support this: https://stackoverflow.com/q/34032262/28465

Fixes #919, #918, #917, #915, #914, #911, #908, #906, #904, #903, #901, #900, #899

RELNOTES=n/a
PiperOrigin-RevId: 338485304
copybara-service bot pushed a commit that referenced this pull request Oct 22, 2020
Process:
  ( for F in common factory service value; do ( mvn org.codehaus.mojo:versions-maven-plugin:2.8.1:update-properties org.codehaus.mojo:versions-maven-plugin:2.8.1:use-latest-releases -f $F/pom.xml ); done && mvn org.codehaus.mojo:versions-maven-plugin:2.8.1:use-latest-versions -f value/src/it/gwtserializer/pom.xml )
  Then undid the Compile-Testing update in value/pom.xml. It somehow breaks things.
  And I undid the google-java-format update in factory/pom.xml. It isn't compatible with JDK8/9, which is what Travis is set up for. (And then I flailed around for 15 minutes because Maven didn't rebuild some files when I changed JDKs, producing mystery failures. Argh. Perhaps we should set `<useIncrementalCompilation>` to `false` everywhere.)
  And *then* I undid the auto-service upgrade in value/processor/pom.xml. It causes problems but only under JDK9: https://travis-ci.org/github/google/auto/jobs/738096563 The error isn't in generated code, so I suspect a compiler bug. (But my quick search didn't find a filed OpenJDK issue.)
  (Someday I will remember -DgenerateBackupPoms=false....)

For some reason, gwtserializer responds to use-latest-versions but not to use-latest-releases, even though it's updating GWT to a release (just as in one of the other POMs).

We don't use use-latest-versions everywhere not just because it could theoretically pick a non-release versions but also because use-latest-versions replaces variable usages like ${guava-version} by inlining the value into them: mojohaus/versions#243

I would have updated the plugins in addition to the deps, but oddly the plugin does not support this: https://stackoverflow.com/q/34032262/28465

Fixes #919, #918, #917, #915, #914, #911, #908, #906, #904, #903, #901, #900, #899

RELNOTES=n/a
PiperOrigin-RevId: 338507900
@cpovirk cpovirk closed this Oct 22, 2020
@dependabot @github
Copy link
Contributor Author

dependabot bot commented on behalf of github Oct 22, 2020

OK, I won't notify you again about this release, but will get in touch when a new version is available.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.

@dependabot dependabot bot deleted the dependabot/maven/factory/com.google.auto.value-auto-value-annotations-1.7.4 branch October 22, 2020 19:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cla: yes dependencies Pull requests that update a dependency file java Pull requests that update Java code
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant