Add log4j-samples-graalvm its own Dependabot entry - #428
Open
ramanathan1504 wants to merge 2 commits into
Open
Conversation
…and ensure correct version resolution
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The
/reactor andlog4j-samples-graalvmare separate Maven projects, each with<version>${revision}</version>and its own<revision>0.0.0-SNAPSHOT</revision>, sharingone
updatesentry viadirectories:.Dependabot resolves
${revision}across both and rewrites the wrong<version>. #426 is the result: its whole diff replaces the reactor's own version, and all 12 modulesthen fail to resolve
log4j-samples:pom:${revision}.One entry per project removes the ambiguity.
Relates to #426, which can be closed.