Provide a more obvious way to not add `sentry` artifact

[Vampire]

Problem Statement

When just using the log4j appender but not using Sentry in code, the plugin still adds the sentry artifact to the implementation configuration.

If you then for example have the dependency analysis gradle plugin in action, it of course complains that there is an unused dependency that should be removed.

As far as I have seen there is no obvious way to not do it while still enriching the other modules.

By reading the sources I found that I can do implementation(platform(libs.sentry.bom)) which - if it contains a version - does exactly skip this artifact adding, but this is not too obvious.

Solution Brainstorm

sentry {
    autoInstallation.sdk = false
}

[linear-code]

GRADLE-87

[lbloder]

Hi @Vampire,
Thank you for your submission.
What kind of setup are you trying to achieve, when do you need the Sentry log4j appender and not the Sentry sdk itself?
Do you want to autoinstall the modules but install the sdk itself manually?

[Vampire]

What kind of setup are you trying to achieve, when do you need the Sentry log4j appender and not the Sentry sdk itself?

For now I only have the appender in my lgo4j configuration and a sentry.properties file to set DSN, release, and default environment during development overridden by system property at runtime.
I do not use Sentry code-wise for now.
So I don't want to have Sentry as dependency, so that also DAGP does not complain about the unused dependency.

As soon as I use Sentry code-wise, I of course also need the SDK dependency.
Whether I then add it manually or get it added by the Gradle plugin does not make much difference.

Do you want to autoinstall the modules

Yes

but install the sdk itself manually?

As said, currently not added at all as not needed.
Once I need it, getting it added manually or by the plugin does not make a difference.