Skip to content

changing snapshot versioning scheme to track the target final release… #45

changing snapshot versioning scheme to track the target final release…

changing snapshot versioning scheme to track the target final release… #45

Triggered via push November 22, 2023 00:10
Status Success
Total duration 1m 40s
Artifacts

maven.yml

on: push
Matrix: build
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 4 warnings
JDK 21
Process completed with exit code 1.
JDK 17
Process completed with exit code 1.
JDK 21
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-java@v1, actions/cache@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
JDK 17
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-java@v1, actions/cache@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
JDK 11
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-java@v1, actions/cache@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
deploy
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/setup-java@v1, actions/cache@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/