-
Notifications
You must be signed in to change notification settings - Fork 47
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
1.6.1 warns about missing dependencies when 1.5.1 did not #231
Labels
Comments
slawekjaranowski
added a commit
that referenced
this issue
Nov 23, 2022
slawekjaranowski
added a commit
that referenced
this issue
Nov 23, 2022
slawekjaranowski
added a commit
that referenced
this issue
Nov 23, 2022
@slawekjaranowski Would it be possible to spin a release of extra-enforcer-rules that contains this fix and all the other updates that have been done in the meantime? |
I can ... I forgot about this fix. |
amottier
added a commit
to amottier/Waarp-All
that referenced
this issue
Jul 4, 2023
Version 1.6.1 fix an issue related to remote repositories not interrogated (see mojohaus/extra-enforcer-rules#225). Version 1.6.2 fix a similar issue: mojohaus/extra-enforcer-rules#231 So updating version from 1.6.0 to 1.6.2. extra-enforcer-rules depends on maven-enforcer-plugin so updating also maven-enforcer-plugin to version 3.2.1.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This is similar to #225 but happens when a local repository is used for some artifacts:
https://github.com/albertus82/earthquake-bulletin/runs/8014689860?check_suite_focus=true#step:4:23
In this specific case the repository is hosted in
${project.baseUri}mvn/repository
and is referenced in the pom.xml asThanks.
The text was updated successfully, but these errors were encountered: