hboutemy commented on PR #206: URL: https://github.com/apache/maven-artifact-plugin/pull/206#issuecomment-4121653549
ok, now I understand the intent (= what should be in the PR description) I love detecting version ranges, I'm torn on failing `artifact:compare`: I know that warnings will be ignored... failing is crude, not really actionable (message `Please fix them to have a fixed version for better reproducibility` is too late on a release), for the first time, rebuilding will manage to reproduce... I would not hesitate on `artifact:check-build-plan`, which is something that happens early, when people try to improve their build I know that I'll have to de-activate `artifact:compare` failure in Reproducible Central what I don't know is "how to report that a rebuild was done now that was successfully matching reference build, BUT it was a lucky non-permanent rebuild" I'll probably have to accept this PR: I love the warning that I'll get when disabling what I'd like after this PR is to see if we can have: - a message of `artifact:compare` in the `.compare` output file (like "fragile dependency version resolution from range") - the same message in `artifact:check-build-plan` -- 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]
