adamsaghy commented on PR #5665:
URL: https://github.com/apache/fineract/pull/5665#issuecomment-4118823265
```
1: Task failed with an exception.
-----------
* What went wrong:
Execution failed for task ':fineract-core:compileTestJava'.
> Compilation failed; see the compiler output below.
warning: No processor claimed any of these annotations:
/org.junit.jupiter.params.provider.ValueSource,/org.junit.jupiter.api.AfterAll,/org.junit.jupiter.api.Test,/org.junit.jupiter.api.extension.ExtendWith,/org.junit.jupiter.api.BeforeAll,/org.junit.jupiter.api.AfterEach,/org.mockito.Mock,/org.junit.jupiter.api.DisplayName,/org.mockito.InjectMocks,/org.junit.jupiter.api.BeforeEach,/org.junit.jupiter.params.provider.CsvSource,/org.junit.jupiter.params.ParameterizedTest,/org.mockito.junit.jupiter.MockitoSettings,/org.mockito.Spy
1 error
Deprecated Gradle features were used in this build, making it incompatible
with Gradle 9.0.
You can use '--warning-mode all' to show the individual deprecation warnings
and determine if they come from your own scripts or plugins.
For more on this, please refer to
https://docs.gradle.org/8.14.3/userguide/command_line_interface.html#sec:command_line_warnings
in the Gradle documentation.
307 actionable tasks: 270 executed, 10 from cache, 27 up-to-date
8 warnings
==============================================================================
2: Task failed with an exception.
-----------
* What went wrong:
Execution failed for task ':fineract-core:checkstyleMain'.
> A failure occurred while executing
org.gradle.api.plugins.quality.internal.CheckstyleAction
> Checkstyle rule violations were found. See the report at:
file:///home/runner/work/fineract/fineract/fineract-core/build/reports/checkstyle/main.html
Checkstyle files with violations: 1
Checkstyle violations by severity: [error:1]
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
