[tycho-4.0.x] Move DependencyArtifacts computation into project types #3186
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
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
Currently DefaultTychoResolver computes the DependencyArtifacts on behalf of the TychoProject and then set these into the project using a context value, this has several drawbacks, e.g as it introduce ordering problem and we need to handle some things special for custom types. Instead the TychoProject itself should compute the dependencies on demand as its concrete implementation knows best how to compute these items and can simply do so on first request. (cherry picked from commit 05bdf27)
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.
Backport
This will backport the following commits from
mastertotycho-4.0.x:Questions ?
Please refer to the Backport tool documentation