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

Less Spotless Gradle Warnings #2614

Merged
merged 4 commits into from
Aug 10, 2021
Merged

Conversation

shemnon
Copy link
Contributor

@shemnon shemnon commented Aug 4, 2021

PR description

Spotless and Gradle 7.x does not play nicely with using a fileTree as a
target and should be using plain strings. This should get rid of the
Execution optimizations have been disabled... warnings.

Changelog

shemnon added 3 commits August 3, 2021 22:32
Spotless and Gradle 7.x does not play nicely with using a fileTree as a
target and should be using plain strings. This should get rid of the
`Execution optimizations have been disabled`... warnings.

Signed-off-by: Danno Ferrin <danno.ferrin@gmail.com>
Signed-off-by: Danno Ferrin <danno.ferrin@gmail.com>
Generated reference test are currently generated into `src`, which is in
violation of the standard maven layouts.  They should be in the `build`
directory as they are artifacts not maintained in source control.

Signed-off-by: Danno Ferrin <danno.ferrin@gmail.com>
@lucassaldanha lucassaldanha enabled auto-merge (squash) August 10, 2021 22:10
@lucassaldanha lucassaldanha merged commit 78c50e9 into hyperledger:main Aug 10, 2021
@shemnon shemnon deleted the lessSpotless branch February 26, 2022 18:42
eum602 pushed a commit to lacchain/besu that referenced this pull request Nov 3, 2023
* Less Spotless Gradle Warnings

Spotless and Gradle 7.x does not play nicely with using a fileTree as a
target and should be using plain strings. This should get rid of the
`Execution optimizations have been disabled`... warnings.

* Move Generated Reference Tests into the `build` dir

Generated reference test are currently generated into `src`, which is in
violation of the standard maven layouts.  They should be in the `build`
directory as they are artifacts not maintained in source control.

Signed-off-by: Danno Ferrin <danno.ferrin@gmail.com>
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.

2 participants