Skip to content
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

Closed
juanpablo-santos opened this issue Feb 22, 2021 · 2 comments

Comments

@juanpablo-santos
Copy link

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?

@arturobernalg
Copy link

H @juanpablo-santos @siom79

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

: Versions of archives indicate a minor change but binary incompatible changes found.

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
@siom79
Copy link
Owner

siom79 commented Mar 6, 2021

Fixed: 0.15.3

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants