[MDEP-650] - dependency:unpack doesn't seem to handle version ranges#11
Closed
alehane wants to merge 9 commits intoapache:masterfrom
Closed
[MDEP-650] - dependency:unpack doesn't seem to handle version ranges#11alehane wants to merge 9 commits intoapache:masterfrom
alehane wants to merge 9 commits intoapache:masterfrom
Conversation
…ck" goal - add tests and improve error handling
…ck" goal - add tests and improve error handling
…- correct file name
Author
|
Apologies, please ignore this request - I've made a couple of really silly errors with it! I'll close and reopen the request with the errors corrected. |
asfgit
pushed a commit
that referenced
this pull request
Sep 29, 2021
[MGPG-81] check format in constructor
|
Resolve #1086 |
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
2 participants
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.
Attempt to enable version range resolution for the dependency:unpack goal by first checking to see whether the version range has already been resolved by the project's dependency resolution. If there is no resolution, attempt to use the DependencyResolver maven component to resolve the range. If resolution is successful, then update the artifactItem object with the resolved version, otherwise, leave the version un-changed.
Tests and verification:
Licence info:
To make clear that you license your contribution under
the Apache License Version 2.0, January 2004
you have to acknowledge this by using the following check-box.
I hereby declare this contribution to be licenced under the Apache License Version 2.0, January 2004
In any other case, please file an Apache Individual Contributor License Agreement.