Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Consider using compileOnlyApi over implementation for compile-time annotations #156

Closed
yuri-sergiichuk opened this issue Nov 19, 2020 · 2 comments
Assignees
Projects

Comments

@yuri-sergiichuk
Copy link
Contributor

The new compileOnlyApi dependency introduced in Gradle v6.7 allows using the new scope for dependencies that must be present while compiling the code, but not required in runtime.

Also, the api part exposes the dependency of the library to the consumers, so they are e.g. able to rely on the same annotations while running their annotation processors with the library.
An example of a dependency that'll benefit from the new scope is ErrorProne annotations. The annotations are required during the compile-time and give hints to other users about the library behavior but are not really used in runtime.

@alexander-yevsyukov alexander-yevsyukov added this to To Do in 1.7 via automation Nov 19, 2020
@yuri-sergiichuk yuri-sergiichuk self-assigned this Dec 2, 2020
@yuri-sergiichuk yuri-sergiichuk moved this from To Do to In Progress in 1.7 Dec 2, 2020
@yuri-sergiichuk
Copy link
Contributor Author

There's a known issue with the license report plugin we're using to generate the license-report.md files, it currently does not support the new compileOnlyApi scope.

@yuri-sergiichuk
Copy link
Contributor Author

All the published libraries are now updated.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
No open projects
1.7
Done
Development

No branches or pull requests

1 participant