Skip to content

introduce parent POM to centrally manage versions #979

introduce parent POM to centrally manage versions

introduce parent POM to centrally manage versions #979

Triggered via push January 22, 2024 08:58
Status Failure
Total duration 7m 31s
Artifacts

maven.yml

on: push
Matrix: build-java-11-project-batches
Matrix: build-java-8-and-17-projects
Fit to window
Zoom out
Zoom in

Annotations

1 error and 5 warnings
Build Java 11 Batch 3 projects
Process completed with exit code 1.
Build Java 8 projects
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/cache@v1, actions/setup-java@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Build Java 17 projects
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/cache@v1, actions/setup-java@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Build Java 11 Batch 3 projects
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/cache@v1, actions/setup-java@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Build Java 11 Batch 1 projects
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/cache@v1, actions/setup-java@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Build Java 11 Batch 2 projects
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/cache@v1, actions/setup-java@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/