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

Gradle deprecation warnings #1984

Closed
squaregoldfish opened this issue Jan 28, 2021 · 1 comment
Closed

Gradle deprecation warnings #1984

squaregoldfish opened this issue Jan 28, 2021 · 1 comment
Assignees
Milestone

Comments

@squaregoldfish
Copy link
Collaborator

Deprecated Gradle features were used in this build, making it incompatible with Gradle 7.0.
Use '--warning-mode all' to show the individual deprecation warnings.
See https://docs.gradle.org/6.6.1/userguide/command_line_interface.html#sec:command_line_warnings

Needs fixing before we get to Gradle 7.

@squaregoldfish squaregoldfish added this to the High Priority milestone Jan 28, 2021
@squaregoldfish
Copy link
Collaborator Author

There is also Flyway v7, which has an option to fail on missing locations. Relevant for: flyway/flyway-test-extensions#68

@squaregoldfish squaregoldfish self-assigned this Nov 15, 2021
squaregoldfish added a commit to squaregoldfish/QuinCe that referenced this issue Nov 15, 2021
squaregoldfish added a commit to squaregoldfish/QuinCe that referenced this issue Nov 15, 2021
Fixed all deprecation warnings for Gravle v7
JUnit tests are now run in parallel
squaregoldfish added a commit that referenced this issue Nov 15, 2021
Fixed all deprecation warnings for Gravle v7
JUnit tests are now run in parallel
squaregoldfish added a commit that referenced this issue Nov 17, 2021
Fixed all deprecation warnings for Gravle v7
JUnit tests are now run in parallel
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant