Inject services into MinimalExternalModuleDependency instances #23232
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.
Fixes #23096
All dependencies which extend
AbstractModuleDependency
should have theirattributesFactory
andcapabilityNotationParser
initialized. This is usually done in theDefaultDependencyFactory
, though now thatMinimalExternalModuleDependency
extendsExternalModuleDependency
and its implements extendAbstractModuleDependency
, we must be sure that we initialize its services when we instantiate them. This PR does that.Further, we ensure we properly copy all fields in instances of
MinimalExternalModuleDependency
when copying them. This ensures we do not leave behind dependency artifacts or other data when adding dependencies to configurations via the projectDependencyHandler
.