Use unique contexts for installer library lookup #190
Merged
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.
This PR fixes a current issue with the generation of the legacy installer profile that causes the tools used in the processor steps to not be included in the
libraries
section, causing the tools to not be downloaded.The fix is to change the context used for calling
temporaryConfiguration
to be unique for each given tool, rather than using a constant context.The use of a constant context meant that each call to
temporaryConfiguration
resulted in the same configuration being returned. AstemporaryConfiguration
only adds the requested libraries on the first use of the configuration (as it checks if the configuration is first empty before adding the requested dependencies), any subsequent invocation with the same context, even with different dependencies as arguments, would just return the configuration from the first invocation unchanged.