RELNOTES=N/A
PiperOrigin-RevId: 709094695

There's more to migrate, this is only a first pass migrating most of SourceFiles and the APIs that call into it.

RELNOTES=N/A
PiperOrigin-RevId: 710093844

….inject.Provider` can be used.

RELNOTES=Support injecting `jakarta.inject.Provider`
PiperOrigin-RevId: 710101199

  * Fixes the name of the proguard file to contain an underscore between the package and simple names (e.g. `test.FooModule` was `testFooModule_LazyClassKeys.pro` and is now `test_FooModule_LazyClassKeys.pro`).
  * Fixes incremental processing by adding the originating element to the `writeResource` call (#4549).
  * Fixes bug where `StringBuilder` was declared outside module for-loop, which could lead to duplicate entries across proguard rules for different modules.
  * Fixed `ClassName#toString()` usage to `ClassName#canonicalName()`, since `toString()` is ambiguous and will silently break things when we migrate to `XClassName`.
  * Added test coverage for the proguard file name and contents.

Fixes #4549

RELNOTES=Fixes #4549: Fixes incremental processing for LazyClassKey proguard files by adding the originating element to the `writeResource` call.
PiperOrigin-RevId: 710126913

At the repository root, the root project 'dagger-parent' configures common build functionality and includes the various projects that will be placed 'gradle-projects', for now only the runtime is configured.

The buildSrc directory is a special Gradle sub-project to share common build logic between sub-projects, it will become more useful in time as the projects gets more complex and shared build logic is needed.

Dependencies and versions are defined in a Version Catalog in gradle/libs.versions.toml, these will eventually need to be validated to be in-sync with Bazel's WORKSPACE.

RELNOTES=N/A
PiperOrigin-RevId: 710702061

The Gradle projects is configured to use JDK 18 toolchain so a new env variable is added for it.

RELNOTES=N/A
PiperOrigin-RevId: 710748526

For now, the flag's default is set to enabled to keep the functionality the same as before. However, in a future release (likely 2.55) we will flip the default to `disabled`.

The new `BindingGraphFactory` contains many bug fixes that still exist in the `LegacyBindingGraphFactory`. However, the new `BindingGraphFactory` does have some behavior changes that may affect users. The biggest change is that we no longer allow a module binding installed in a component to float to a subcomponent to satisfy missing bindings. See the javadoc in `CompilerOptions` for more details.

RELNOTES=N/A
PiperOrigin-RevId: 710805160

…onvention plugin.

Also trying to keep libs.versions.toml ordered alphabetically.

RELNOTES=N/A
PiperOrigin-RevId: 711866498

RELNOTES=N/A
PiperOrigin-RevId: 712608237

Only adds the plugin and POM configuration enabling publishing to local repository, not yet configured for actual world publishing.

RELNOTES=N/A
PiperOrigin-RevId: 713019870

In addition to adding documentation, this CL changes the compiler option name from `useLegacyBindingGraphFactory` to `useBindingGraphFix` to flip the default (it's more intuitive when disabled means "old behavior" and enabled means "new behavior") and to give the name more meaning from a user's perspective (useLegacyBindingGraphFactory likely doesn't mean much for users).

RELNOTES=N/A
PiperOrigin-RevId: 713455646

The validator (https://github.com/Kotlin/binary-compatibility-validator) will help us track public API changes and validate that the conversion from Java to Kotlin does not cause any breakage.

API validation is part of the Gradle build process and will fail the build if API changes are done but not reflected in the API file. To update the API file execute `./gradlew apiDump` and commit the .api file for review along with the code changes.

RELNOTES=N/A
PiperOrigin-RevId: 713662828