fix(deps): update dependency dnsjava:dnsjava to v3 #2897
main.yml
on: pull_request
Matrix Preparation
5s
Error Prone (JDK 17)
4m 51s
Matrix: test
Annotations
5 errors and 2 warnings
Error Prone (JDK 17)
Could not determine the dependencies of task ':src:dist:compileJava'.
> Could not resolve all dependencies for configuration ':src:dist:compileClasspath'.
> Checksum/PGP violations detected on resolving configuration :src:dist:runtimeClasspath
Trusted PGP keys for group dnsjava are [3e1ac64f4e34e290503c90323449ec3ac2efe8aa], however artifact is signed by [e06a36f67d8c1bd13f1f278d0ca7139cbc7026f9] only:
dnsjava:dnsjava:3.6.3 (pgp=[e06a36f67d8c1bd13f1f278d0ca7139cbc7026f9], sha512=[computation skipped])
There might be more checksum violations, however, current configuration specifies the build to fail on the first violation.
You might use the following properties:
* -PchecksumIgnore temporary disables checksum-dependency-plugin (e.g. to try new dependencies)
* -PchecksumUpdate updates checksum.xml and it will fail after the first violation so you can review the diff
* -PchecksumUpdateAll (insecure) updates checksum.xml with all the new discovered checksums
* -PchecksumFailOn=build_finish (insecure) It will postpone the failure till the build finish
It will collect all the violations, however untrusted code might be executed (e.g. from a plugin)
You can find updated checksum.xml file at /home/runner/work/jmeter/jmeter/build/checksum/checksum.xml.
You might add -PchecksumUpdate to update root checksum.xml file.
|
21, microsoft, same hashcode, windows, UTC, tr_TR
Could not determine the dependencies of task ':src:dist:javadocAggregate'.
> Could not resolve all dependencies for configuration ':src:protocol:http:compileClasspath'.
> Checksum/PGP violations detected on resolving configuration :src:protocol:http:runtimeClasspath
Trusted PGP keys for group dnsjava are [3e1ac64f4e34e290503c90323449ec3ac2efe8aa], however artifact is signed by [e06a36f67d8c1bd13f1f278d0ca7139cbc7026f9] only:
dnsjava:dnsjava:3.6.3 (pgp=[e06a36f67d8c1bd13f1f278d0ca7139cbc7026f9], sha512=[computation skipped])
There might be more checksum violations, however, current configuration specifies the build to fail on the first violation.
You might use the following properties:
* -PchecksumIgnore temporary disables checksum-dependency-plugin (e.g. to try new dependencies)
* -PchecksumUpdate updates checksum.xml and it will fail after the first violation so you can review the diff
* -PchecksumUpdateAll (insecure) updates checksum.xml with all the new discovered checksums
* -PchecksumFailOn=build_finish (insecure) It will postpone the failure till the build finish
It will collect all the violations, however untrusted code might be executed (e.g. from a plugin)
You can find updated checksum.xml file at D:\a\jmeter\jmeter\build\checksum\checksum.xml.
You might add -PchecksumUpdate to update root checksum.xml file.
|
17, temurin, macos, America/New_York, tr_TR, stress JIT
Could not determine the dependencies of task ':src:dist:javadocAggregate'.
> Could not resolve all dependencies for configuration ':src:protocol:http:compileClasspath'.
> Checksum/PGP violations detected on resolving configuration :src:protocol:http:runtimeClasspath
Trusted PGP keys for group dnsjava are [3e1ac64f4e34e290503c90323449ec3ac2efe8aa], however artifact is signed by [e06a36f67d8c1bd13f1f278d0ca7139cbc7026f9] only:
dnsjava:dnsjava:3.6.3 (pgp=[e06a36f67d8c1bd13f1f278d0ca7139cbc7026f9], sha512=[computation skipped])
There might be more checksum violations, however, current configuration specifies the build to fail on the first violation.
You might use the following properties:
* -PchecksumIgnore temporary disables checksum-dependency-plugin (e.g. to try new dependencies)
* -PchecksumUpdate updates checksum.xml and it will fail after the first violation so you can review the diff
* -PchecksumUpdateAll (insecure) updates checksum.xml with all the new discovered checksums
* -PchecksumFailOn=build_finish (insecure) It will postpone the failure till the build finish
It will collect all the violations, however untrusted code might be executed (e.g. from a plugin)
You can find updated checksum.xml file at /Users/runner/work/jmeter/jmeter/build/checksum/checksum.xml.
You might add -PchecksumUpdate to update root checksum.xml file.
|
21, temurin, windows, Pacific/Chatham, tr_TR
Could not determine the dependencies of task ':src:dist:javadocAggregate'.
> Could not resolve all dependencies for configuration ':src:protocol:http:compileClasspath'.
> Checksum/PGP violations detected on resolving configuration :src:protocol:http:runtimeClasspath
Trusted PGP keys for group dnsjava are [3e1ac64f4e34e290503c90323449ec3ac2efe8aa], however artifact is signed by [e06a36f67d8c1bd13f1f278d0ca7139cbc7026f9] only:
dnsjava:dnsjava:3.6.3 (pgp=[e06a36f67d8c1bd13f1f278d0ca7139cbc7026f9], sha512=[computation skipped])
There might be more checksum violations, however, current configuration specifies the build to fail on the first violation.
You might use the following properties:
* -PchecksumIgnore temporary disables checksum-dependency-plugin (e.g. to try new dependencies)
* -PchecksumUpdate updates checksum.xml and it will fail after the first violation so you can review the diff
* -PchecksumUpdateAll (insecure) updates checksum.xml with all the new discovered checksums
* -PchecksumFailOn=build_finish (insecure) It will postpone the failure till the build finish
It will collect all the violations, however untrusted code might be executed (e.g. from a plugin)
You can find updated checksum.xml file at D:\a\jmeter\jmeter\build\checksum\checksum.xml.
You might add -PchecksumUpdate to update root checksum.xml file.
|
17, zulu, macos, UTC, de_DE
Could not determine the dependencies of task ':src:dist:javadocAggregate'.
> Could not resolve all dependencies for configuration ':src:protocol:http:compileClasspath'.
> Checksum/PGP violations detected on resolving configuration :src:protocol:http:runtimeClasspath
Trusted PGP keys for group dnsjava are [3e1ac64f4e34e290503c90323449ec3ac2efe8aa], however artifact is signed by [e06a36f67d8c1bd13f1f278d0ca7139cbc7026f9] only:
dnsjava:dnsjava:3.6.3 (pgp=[e06a36f67d8c1bd13f1f278d0ca7139cbc7026f9], sha512=[computation skipped])
There might be more checksum violations, however, current configuration specifies the build to fail on the first violation.
You might use the following properties:
* -PchecksumIgnore temporary disables checksum-dependency-plugin (e.g. to try new dependencies)
* -PchecksumUpdate updates checksum.xml and it will fail after the first violation so you can review the diff
* -PchecksumUpdateAll (insecure) updates checksum.xml with all the new discovered checksums
* -PchecksumFailOn=build_finish (insecure) It will postpone the failure till the build finish
It will collect all the violations, however untrusted code might be executed (e.g. from a plugin)
You can find updated checksum.xml file at /Users/runner/work/jmeter/jmeter/build/checksum/checksum.xml.
You might add -PchecksumUpdate to update root checksum.xml file.
|
Matrix Preparation
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
Error Prone (JDK 17)
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|