Bump libraryVersion.dagger from 2.18 to 2.28

[dependabot-preview]

Bumps libraryVersion.dagger from 2.18 to 2.28.
Updates dagger from 2.18 to 2.28

Release notes

Sourced from dagger's releases.

Dagger 2.27

What's New

1. Fix #955: No longer generate MembersInjectors for types without local injection sites. (20f6442f)
2. Fix #1414: Allow multiple scoped component dependencies (113c498e)
3. Fix #1734: Add support constructor with content layout id for AndroidX (22b27266)
4. Fix #1740: Remove a usage of Guava API not available in the '-android' variant in case of processor classpath conflicts. (bfb87d5b)
5. Fix #1665: Add an explicit check for member injection of Kotlin object classes rather than crashing. (550d6969)
6. Fix: #1612: Fix duplicate binding errors when a component dependency has the same method defined multiple times via multiple interfaces (0bb69e91)

Experimental Error Message Format

This release includes a flag for using the new experimental error message format. The format and some content of error messages will be changed with this flag in order to improve readability. Please leave feedback on issue #1769. Pending feedback, this format will eventually become the default and replace current error messages.

To opt-in to the new format use -Adagger.experimentalDaggerErrorMessages=enabled.

Currently, this flag:

• Shortens all class names to the simple class name. A legend is output at the bottom of the errors to map short names to fully qualified names.
• Reports errors as a single error for each root component.
• Adds color to error tags to visibly separate individual errors
• Reduces some extraneous information from some messages.

Dagger 2.26

What's new

1. Fix #1700: Remove usages of non-Android Guava APIs. (0925e8f7)
2. Fix #1720: Fix incremental dagger-android-processor in kapt when using dagger.android.experimentalUseStringKeys. (6a0ce588)
3. Fix #1721: Migrate dagger-android to AndroidX. (f45213ea)
4. Better support for binding declarations within Kotlin companion objects of @Module annotated classes. (8190c7c1)

Known breaking changes

Companion object modules are no longer allowed on Component#modules list (8190c7c1)

It is now an error to add an @Module annotated companion object class to Component#modules (or Subcomponent#modules) list. Instead, only the outer class should be added to the module list.

// Only add this class to the Component#modules list.
@Module
abstract class FooModule {
  @Binds abstract fun bindFoo(impl: FooImpl): Foo
// @Module is no longer needed here!
companion object {
// @JvmStatic is no longer needed here!
@Provides fun provideBar(): Bar = Bar()
}
}

Note: For backwards compatibility, we still allow @Module on the companion object and @JvmStatic on the provides methods. However, @Module on the companion object is now a no-op and all of its attributes (e.g. "includes") will be ignored. In future releases, we will make it an error to use @Module on a companion object.

... (truncated)

Commits

• d96c543 2.28 release
• c1ddd0c Update Hilt Gradle plugin to publish sources and javadoc jars.
• 65be940 Add the <parent> and <scm><tag> to the Hilt Gradle plugin POM
• 194fbce Add javadoc and java srcs jars for Hilt android compiler and Dagger lint.
• 41b0b92 internal refactor
• 3a169af internal refactor
• 79cabea Update error message when app is not Hilt injected.
• 9fff4bf Move tests to sharedTest and configure to run with both test and androidTest
• 34193b7 Better error message if reflection fails to suggest adding hilt compiler buil...
• e1f4243 Add try-finally around MarkThatRulesRanRule's evaluate() to ensure we clear s...
• Additional commits viewable in compare view

Updates dagger-compiler from 2.18 to 2.28

Release notes

Sourced from dagger-compiler's releases.

Dagger 2.27

What's New

1. Fix #955: No longer generate MembersInjectors for types without local injection sites. (20f6442f)
2. Fix #1414: Allow multiple scoped component dependencies (113c498e)
3. Fix #1734: Add support constructor with content layout id for AndroidX (22b27266)
4. Fix #1740: Remove a usage of Guava API not available in the '-android' variant in case of processor classpath conflicts. (bfb87d5b)
5. Fix #1665: Add an explicit check for member injection of Kotlin object classes rather than crashing. (550d6969)
6. Fix: #1612: Fix duplicate binding errors when a component dependency has the same method defined multiple times via multiple interfaces (0bb69e91)

Experimental Error Message Format

This release includes a flag for using the new experimental error message format. The format and some content of error messages will be changed with this flag in order to improve readability. Please leave feedback on issue #1769. Pending feedback, this format will eventually become the default and replace current error messages.

To opt-in to the new format use -Adagger.experimentalDaggerErrorMessages=enabled.

Currently, this flag:

• Shortens all class names to the simple class name. A legend is output at the bottom of the errors to map short names to fully qualified names.
• Reports errors as a single error for each root component.
• Adds color to error tags to visibly separate individual errors
• Reduces some extraneous information from some messages.

Dagger 2.26

What's new

1. Fix #1700: Remove usages of non-Android Guava APIs. (0925e8f7)
2. Fix #1720: Fix incremental dagger-android-processor in kapt when using dagger.android.experimentalUseStringKeys. (6a0ce588)
3. Fix #1721: Migrate dagger-android to AndroidX. (f45213ea)
4. Better support for binding declarations within Kotlin companion objects of @Module annotated classes. (8190c7c1)

Known breaking changes

Companion object modules are no longer allowed on Component#modules list (8190c7c1)

It is now an error to add an @Module annotated companion object class to Component#modules (or Subcomponent#modules) list. Instead, only the outer class should be added to the module list.

// Only add this class to the Component#modules list.
@Module
abstract class FooModule {
  @Binds abstract fun bindFoo(impl: FooImpl): Foo
// @Module is no longer needed here!
companion object {
// @JvmStatic is no longer needed here!
@Provides fun provideBar(): Bar = Bar()
}
}

Note: For backwards compatibility, we still allow @Module on the companion object and @JvmStatic on the provides methods. However, @Module on the companion object is now a no-op and all of its attributes (e.g. "includes") will be ignored. In future releases, we will make it an error to use @Module on a companion object.

... (truncated)

Commits

• d96c543 2.28 release
• c1ddd0c Update Hilt Gradle plugin to publish sources and javadoc jars.
• 65be940 Add the <parent> and <scm><tag> to the Hilt Gradle plugin POM
• 194fbce Add javadoc and java srcs jars for Hilt android compiler and Dagger lint.
• 41b0b92 internal refactor
• 3a169af internal refactor
• 79cabea Update error message when app is not Hilt injected.
• 9fff4bf Move tests to sharedTest and configure to run with both test and androidTest
• 34193b7 Better error message if reflection fails to suggest adding hilt compiler buil...
• e1f4243 Add try-finally around MarkThatRulesRanRule's evaluate() to ensure we clear s...
• Additional commits viewable in compare view

Updates dagger-android-support from 2.18 to 2.28

Release notes

Sourced from dagger-android-support's releases.

Dagger 2.27

What's New

1. Fix #955: No longer generate MembersInjectors for types without local injection sites. (20f6442f)
2. Fix #1414: Allow multiple scoped component dependencies (113c498e)
3. Fix #1734: Add support constructor with content layout id for AndroidX (22b27266)
4. Fix #1740: Remove a usage of Guava API not available in the '-android' variant in case of processor classpath conflicts. (bfb87d5b)
5. Fix #1665: Add an explicit check for member injection of Kotlin object classes rather than crashing. (550d6969)
6. Fix: #1612: Fix duplicate binding errors when a component dependency has the same method defined multiple times via multiple interfaces (0bb69e91)

Experimental Error Message Format

This release includes a flag for using the new experimental error message format. The format and some content of error messages will be changed with this flag in order to improve readability. Please leave feedback on issue #1769. Pending feedback, this format will eventually become the default and replace current error messages.

To opt-in to the new format use -Adagger.experimentalDaggerErrorMessages=enabled.

Currently, this flag:

• Shortens all class names to the simple class name. A legend is output at the bottom of the errors to map short names to fully qualified names.
• Reports errors as a single error for each root component.
• Adds color to error tags to visibly separate individual errors
• Reduces some extraneous information from some messages.

Dagger 2.26

What's new

1. Fix #1700: Remove usages of non-Android Guava APIs. (0925e8f7)
2. Fix #1720: Fix incremental dagger-android-processor in kapt when using dagger.android.experimentalUseStringKeys. (6a0ce588)
3. Fix #1721: Migrate dagger-android to AndroidX. (f45213ea)
4. Better support for binding declarations within Kotlin companion objects of @Module annotated classes. (8190c7c1)

Known breaking changes

Companion object modules are no longer allowed on Component#modules list (8190c7c1)

It is now an error to add an @Module annotated companion object class to Component#modules (or Subcomponent#modules) list. Instead, only the outer class should be added to the module list.

// Only add this class to the Component#modules list.
@Module
abstract class FooModule {
  @Binds abstract fun bindFoo(impl: FooImpl): Foo
// @Module is no longer needed here!
companion object {
// @JvmStatic is no longer needed here!
@Provides fun provideBar(): Bar = Bar()
}
}

Note: For backwards compatibility, we still allow @Module on the companion object and @JvmStatic on the provides methods. However, @Module on the companion object is now a no-op and all of its attributes (e.g. "includes") will be ignored. In future releases, we will make it an error to use @Module on a companion object.

... (truncated)

Commits

• d96c543 2.28 release
• c1ddd0c Update Hilt Gradle plugin to publish sources and javadoc jars.
• 65be940 Add the <parent> and <scm><tag> to the Hilt Gradle plugin POM
• 194fbce Add javadoc and java srcs jars for Hilt android compiler and Dagger lint.
• 41b0b92 internal refactor
• 3a169af internal refactor
• 79cabea Update error message when app is not Hilt injected.
• 9fff4bf Move tests to sharedTest and configure to run with both test and androidTest
• 34193b7 Better error message if reflection fails to suggest adding hilt compiler buil...
• e1f4243 Add try-finally around MarkThatRulesRanRule's evaluate() to ensure we clear s...
• Additional commits viewable in compare view

Updates dagger-android-processor from 2.18 to 2.28

Release notes

Sourced from dagger-android-processor's releases.

Dagger 2.27

What's New

1. Fix #955: No longer generate MembersInjectors for types without local injection sites. (20f6442f)
2. Fix #1414: Allow multiple scoped component dependencies (113c498e)
3. Fix #1734: Add support constructor with content layout id for AndroidX (22b27266)
4. Fix #1740: Remove a usage of Guava API not available in the '-android' variant in case of processor classpath conflicts. (bfb87d5b)
5. Fix #1665: Add an explicit check for member injection of Kotlin object classes rather than crashing. (550d6969)
6. Fix: #1612: Fix duplicate binding errors when a component dependency has the same method defined multiple times via multiple interfaces (0bb69e91)

Experimental Error Message Format

This release includes a flag for using the new experimental error message format. The format and some content of error messages will be changed with this flag in order to improve readability. Please leave feedback on issue #1769. Pending feedback, this format will eventually become the default and replace current error messages.

To opt-in to the new format use -Adagger.experimentalDaggerErrorMessages=enabled.

Currently, this flag:

• Shortens all class names to the simple class name. A legend is output at the bottom of the errors to map short names to fully qualified names.
• Reports errors as a single error for each root component.
• Adds color to error tags to visibly separate individual errors
• Reduces some extraneous information from some messages.

Dagger 2.26

What's new

1. Fix #1700: Remove usages of non-Android Guava APIs. (0925e8f7)
2. Fix #1720: Fix incremental dagger-android-processor in kapt when using dagger.android.experimentalUseStringKeys. (6a0ce588)
3. Fix #1721: Migrate dagger-android to AndroidX. (f45213ea)
4. Better support for binding declarations within Kotlin companion objects of @Module annotated classes. (8190c7c1)

Known breaking changes

Companion object modules are no longer allowed on Component#modules list (8190c7c1)

It is now an error to add an @Module annotated companion object class to Component#modules (or Subcomponent#modules) list. Instead, only the outer class should be added to the module list.

// Only add this class to the Component#modules list.
@Module
abstract class FooModule {
  @Binds abstract fun bindFoo(impl: FooImpl): Foo
// @Module is no longer needed here!
companion object {
// @JvmStatic is no longer needed here!
@Provides fun provideBar(): Bar = Bar()
}
}

Note: For backwards compatibility, we still allow @Module on the companion object and @JvmStatic on the provides methods. However, @Module on the companion object is now a no-op and all of its attributes (e.g. "includes") will be ignored. In future releases, we will make it an error to use @Module on a companion object.

... (truncated)

Commits

• d96c543 2.28 release
• c1ddd0c Update Hilt Gradle plugin to publish sources and javadoc jars.
• 65be940 Add the <parent> and <scm><tag> to the Hilt Gradle plugin POM
• 194fbce Add javadoc and java srcs jars for Hilt android compiler and Dagger lint.
• 41b0b92 internal refactor
• 3a169af internal refactor
• 79cabea Update error message when app is not Hilt injected.
• 9fff4bf Move tests to sharedTest and configure to run with both test and androidTest
• 34193b7 Better error message if reflection fails to suggest adding hilt compiler buil...
• e1f4243 Add try-finally around MarkThatRulesRanRule's evaluate() to ensure we clear s...
• Additional commits viewable in compare view

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)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
• @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

• Update frequency (including time of day and day of week)
• Pull request limits (per update run and/or open at any time)
• Out-of-range updates (receive only lockfile updates, if desired)
• Security updates (receive only security updates, if desired)

[dependabot-preview]

Superseded by #94.