RELNOTES=N/A
PiperOrigin-RevId: 740488311

RELNOTES=N/A
PiperOrigin-RevId: 740802635

RELNOTES=N/A
PiperOrigin-RevId: 741161983

RELNOTES=n/a
PiperOrigin-RevId: 741219198

This feature was originally added to allow Hilt to continue processing and potentially generate files that would otherwise show up as missing symbols and potentially pollute the error logs. However, the implementation of this feature doesn't work with KSP2 which will crash if elements are accessed outside of the round they were created. We could work around this issue by storing identifying information about elements (e.g. parameter name -> method signature -> class name) to recreate elements in the current round; but we decided to just remove this feature since it's not clear it has a lot of benefit.

RELNOTES=N/A
PiperOrigin-RevId: 741279228

This method is private, but is called from the public method `BindingGraph#entryPointEdgesDependingOnBinding(MaybeBinding)` and without memoization will create a new (identical) graph each time it's called.

RELNOTES=N/A
PiperOrigin-RevId: 742410107

RELNOTES=N/A
PiperOrigin-RevId: 742453757

RELNOTES=n/a
PiperOrigin-RevId: 742852939

This CL also creates a wrapper class for XTypeSpec.Builder, which has a few benefits:

  1. Has method overloads for both JavaPoet and XPoet
  2. Has method API that is very similar to JavaPoet
  3. Allows adding in functionality specific to all Dagger generated types (e.g. setting common default values for all of the builders).

The first two benefits are mostly for migration purposes, but my thought is that we'll likely keep these builders around even after the migration because it just makes it easier to customize the API to Dagger's needs.

RELNOTES=N/A
PiperOrigin-RevId: 743193970

RELNOTES=N/A
PiperOrigin-RevId: 743228588

PiperOrigin-RevId: 743682120

This CL adds a new utility class, `XFunSpecs.java`, which includes a wrapper of `XFunSpec.Builder` to expose an API that's easier for migration. In particular, the wrapper is very similar to JavaPoet's API, and it allows setting input as both JavaPoet and/or XPoet.

The JavaPoet APIs are marked as `@Deprecated` and they will be cleaned up in a future CL.

RELNOTES=N/A
PiperOrigin-RevId: 745249141

RELNOTES=N/A
PiperOrigin-RevId: 745621882

This was motivated by #4658.

The lock file has [a few benefits](https://github.com/bazel-contrib/rules_jvm_external?tab=readme-ov-file#pinning-artifacts-and-integration-with-bazels-downloader):

  * Explicitly keeps track of versions (which might be different than the versions we declare in MODULE.bazel).
  * Verifies artifacts against their checksums
  * Improves caching of external dependencies.

RELNOTES=N/A
PiperOrigin-RevId: 746316091

Fixes #4658

Typically, this shouldn't be an issue because we declared Guava 33.3.1 in [Dagger's pom file](https://repo1.maven.org/maven2/com/google/dagger/dagger-compiler/2.56.1/dagger-compiler-2.56.1.pom), which should force downstream users to get the upgraded dependency. However, a bug in Gradle (https://youtrack.jetbrains.com/issue/KT-76388) is currently pulling in Guava 32.1.2 onto the ClassLoader first resulting in the following error:

```
java.lang.NoSuchMethodError: 'com.google.common.collect.ImmutableSet com.google.common.graph.Graphs.reachableNodes(com.google.common.graph.Graph, java.lang.Object)'
```

RELNOTES=Fixes #4658: Pin version of Guava to the one specified in our maven.install (i.e. v33.0.0).
PiperOrigin-RevId: 746529208

…e arguments.

Fixes #4676

This feature causes issues for types whose kotlin and java representation have mismatched shapes, e.g. suspend function.

RELNOTES=Fixes #4676: Disable support for type-use nullability on generated jave type arguments.
PiperOrigin-RevId: 748081674

This CL adds a new utility class, XPropertySpecs.java, which includes a wrapper of XPropertySpec.Builder to expose an API that's easier for migration. In particular, the wrapper is very similar to JavaPoet's API, and it allows setting input as both JavaPoet and/or XPoet.

The JavaPoet APIs are marked as @deprecated and they will be cleaned up in a future CL.

RELNOTES=N/A
PiperOrigin-RevId: 748332454

RELNOTES=N/A
PiperOrigin-RevId: 748367336