Artifact tags, support for shaded output and source attachments. #4631
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
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.
This PR extends the still private API for project artifacts with 'tags', which are implementation- or technology-dependent labels. Currently tags are used to mark artifact that are 'shaded' (with dependencies included) or 'base' so the client can select processed or original artifacts.
Maven, for example, can produce multiple shaded artifacts with different classifiers or can replace the main project's artifact with the shaded one. Now the client is able to find or at least enumerate the originals, the shaded artifact and since they are tagged, the client can pick the files it needs.
Several abstract classifiers are defined (sources, test-sources, tests), they are mapped to build system's own classifiers by the implementation.