Fix IVY-1478 #17
Merged
Fix IVY-1478 #17
Conversation
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
…n while dealing with unpacked artifacts
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 commit here fixes the issue reported in https://issues.apache.org/jira/browse/IVY-1478 and also includes a test case to verify the changes.
The fix involves setting the unpacked artifact reference within the
ArtifactDownloadReportwhen the unpacking happens. In the absence of reference to the unpacked artifact in theArtifactDownloadReport, theRetrieveEnginewhile dealing with unpacked artifacts, explicitly uses thePackagingManagerfor getting hold of the unpacked artifact.This commit includes a change in the method signature of
PackagingManager.unpackArtifactwhich now returns a reference to the unpackedArtifactwhereas previously the method return type wasvoid. This change however is still binary compatible.