-
Notifications
You must be signed in to change notification settings - Fork 107
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
Starting with 0.15.0 maven plugin fails if previous version of an artifact can't be resolved #283
Comments
Yep, the new version (0.15.0) breaks the builds when unable to find or does not exist the binary. it seem is ignoring the ignoreNonResolvableArtifacts param
|
siom79
added a commit
that referenced
this issue
Mar 6, 2021
… logged, the build is not broken #283 the ignoreMissingArtifact option is evaluated properly when the artifact is missing
Fixed: 0.15.3 |
This was referenced Mar 15, 2021
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
With 0.14.4, missing artifacts don't break the build, whereas with 0.15.0, they do. This change of behaviour isn't mentioned on the release notes and the
ignoreNonResolvableArtifacts
parameter doesn't seem to be taken into account, so maybe this change wasn't intentional?The text was updated successfully, but these errors were encountered: