build: add helper for installing projects for a single subdirectory#11886
Open
build: add helper for installing projects for a single subdirectory#11886
Conversation
Contributor
Author
|
This actually isn't necessary if you run Originally, this was failing using the |
3ca5089 to
5bdeab6
Compare
Contributor
Author
|
Turns out we do need to detect the list of projects to run as we can't use |
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
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.
With split unit tests, this allows for determining and installing all minimal set of defined artifacts.
The python script builds a dependency tree of java artifacts that exist in the repository and compiles the list of dependencies (including boms used for dependency management). It then uses the existing helper for installing a list of modules to install these in parallel via maven's project reactor (to ensure build order).
This is not yet needed by split repositories like java-logging, but will be for ones like bigquery which have dependencies on other artifacts within the monorepo. This will also be useful when there are more layers of the java release train migrated into the monorepo.