-
Notifications
You must be signed in to change notification settings - Fork 9
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
Comparison of Trusted Checksums and Maven-Lockfile #954
Comments
Summary/continuation:
|
Example of
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Features
Maven-Lockfile
Trusted Checksums
Both
The main thing missing from Trusted Checksums is the ability to download the specific versions specified. If a version range is specified some manual work is required to check the specific version of the jar and specify that one in the pom.xml.
Suggestion: Maven lockfile could (maybe an optional parameter) setup the project to use trusted checksums.
Test on maven-lockfile
When run on the maven-lockfile project the following results are obtained.
Trusted Checksums recorded 1222 checksums, where 779 are checksums for
.pom
files.Maven Lockfile recorded 300 checksums.
All checksums recorded in the lockfile are also recorded in the trusted checksums.
These checksums (filtered to only include jars) are in Trusted Checksums but missing in the lockfiles:
The text was updated successfully, but these errors were encountered: