FR: Declare some artifacts as conventionally compileOnly about dependency-analysis-gradle-plugin

[autonomousapps]

In the particular case of auto-value-annotations, I took a look at the source, as well as the published jar, and see that all of the classes are annotations with either CLASS or SOURCE retention policies. So I think I might be able to automatically detect a case like this and not erroneously suggest that a compileOnly dep be available at runtime. In fact, I can also imagine detecting that such a dep is available at runtime but doesn't need to be (can be compileOnly).

Can you think of any dependencies that are only required at compile-time but which don't only contain CLASS/SOURCE annotations?

[ZacSweers]

There are some annotations that use enums for their members that wouldn't work with that assumption :/.

…

On Thu, Mar 5, 2020 at 1:02 AM Tony Robalik ***@***.***> wrote: In the particular case of auto-value-annotations, I took a look at the source <https://github.com/google/auto/tree/master/value/src/main/java/com/google/auto/value>, as well as the published jar <https://mvnrepository.com/artifact/com.google.auto.value/auto-value-annotations/1.7>, and see that all of the classes are annotations with either CLASS or SOURCE retention policies. So I think I might be able to automatically detect a case like this and not erroneously suggest that a compileOnly dep be available at runtime. In fact, I can also imagine detecting that such a dep is available at runtime but doesn't need to be (can be compileOnly). Can you think of any dependencies that are only required at compile-time but which *don't* only contain CLASS/SOURCE annotations? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#70>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAKMJPU2RD533XQVYQHMQSLRF455XANCNFSM4LB2SPNQ> .

[autonomousapps]

I wrote up some thoughts on what a "for-compilation-only jar" algorithm might look like. Feedback?

Jar must only contain:

1. Annotation classes with CLASS or SOURCE retention policies (or no policy => CLASS is default).
2. 1, plus types that only exist to provide a sort of "namespace". For example, @org.jetbrains.annotations.ApiStatus has no members. It only has inner classes which are themselves annotations that comply with 1.
3. 1 and 2, plus types that are only used by the annotations in the jar that comply with 1. For example, the @org.intellij.lang.annotations.PrintFormat annotation uses a class (in this case defined in the same file), org.intellij.lang.annotations.PrintFormatPattern. The assumption here is that such classes (PrintFormatPattern) are only required during compilation, for their associated compile-only annotations.

[autonomousapps]

Going to close this for now, based on compileOnly support provided with https://github.com/autonomousapps/dependency-analysis-android-gradle-plugin/blob/master/CHANGELOG.md#version-0230