-
Notifications
You must be signed in to change notification settings - Fork 860
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
Maven: Improve dependency resolution (for example for annotation processors like lombok) #8057
Merged
matthiasblaesing
merged 1 commit into
apache:master
from
matthiasblaesing:maven_dependency_management
Dec 22, 2024
+129
−3
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains 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
This file contains 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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Note that the compiler plugin your comment refers to defaults to
jar
type, if theitem.getType()
is not defned.The usage in maven-compiler suggests that each Plugin can choose whatever default it wants :( for its dependencies ... but as long as maven-compiler-plugin is used, any
compile
scope type-less artifact has to be `jar' (otherwise compilation would fail).Could be solved with an additional
type
parameter that would default tojar
.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't get what you mean. Do you mean the type filter should not be there? Could please give a sample?
Edit: What is wrong here, is that I use the newly created dependency to early. I'm doing a fix right now.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Apologies for unclear wording; maybe code would help to understand the intent/difference:
jar
if not specified in thedependency
(assuming the dep mgmt has type resolved before this code executes ? not sure about this)What do you think ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the update, but I don't think it is necessary. Both sides of the comparison are instances of
org.apache.maven.model.Dependency
. That class is generated from this:https://github.com/apache/maven/blob/maven-3.9.9/maven-model/src/main/mdo/maven.mdo#L1096-L1109
and the decompiler gives me the expected:
The type is
jar
unless overridden. So I don't see howgetType
can return null, unless explicitly set from the java side and if not specificied will bejar
.I moved the version update after the initialization from user input, so that we get the Dependency in a state as far initialized as the user did.
I would change/set the scope at least I don't see a use there. For dependency resolution I know that
take part, I never saw scope, so I would currently not mess with that.
So I think the now pushed version should be safe.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for your explanation/patience