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

Put lombok in the provided scope #769

Merged
merged 1 commit into from
Feb 11, 2022

Conversation

vierbergenlars
Copy link
Contributor

The lombok annotation processor should be placed in the provided scope,
so its dependency is not propagated to projects that depend on
spring-content.

This matches with the installation instructions: https://projectlombok.org/setup/maven

Fixes #768

@CLAassistant
Copy link

CLAassistant commented Feb 9, 2022

CLA assistant check
All committers have signed the CLA.

The lombok annotation processor should be placed in the provided scope,
so its dependency is not propagated to projects that depend on
spring-content.

For projects where lombok is only used in tests, it is placed in the
test scope.

Fixes paulcwarren#768
@vierbergenlars
Copy link
Contributor Author

It looks like some spring-content-examples rely on that lombok on the classpath as well.

@paulcwarren
Copy link
Owner

Yup. I will fix those today and re-commit to get the checks green.

@paulcwarren paulcwarren merged commit d7d9124 into paulcwarren:main Feb 11, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Lombok dependency is exposed to consumers
3 participants