[EXPERIMENT] Expose depMgr to use with Maven #1000
Closed
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.
We have 3 of them, but we use always "classic" that behaves like Maven2 (with all it's shortocomings!).
Changes:
This is just an experiment for issues like:
Adds
-Dmaven.resolver.dependencyManager
param with accepted values "classic" (the default every Maven3 used so far), "default" and "transitive".Values are:
Reproducer output with 3 of them: