Switch to using Configuration Capabilities for exporting data - #60
Merged
Conversation
mcumings
marked this pull request as ready for review
August 14, 2026 01:17
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
2 participants
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.
Changes the plugin implementation's mechanism for sharing data between project modules in order to avoid the problems which were encountered in eBay/metrics-for-develocity-plugin#102.
Specifically, using configurations with only attributes to distinguish them runs into resolution-time issues:
A lack of attribute definition on a configuration does NOT result in a match rejection. A lack of attribute value acts more like a wildcard accept, resulting in the consumer potentially matching against incorrect configurations. This becomes an issue when multiple plugins publish configurations, as there is no way to filter these out of the matching algorithm and Gradle can fail due to being left with ambiguous options.
TL;DR: There is no decent way for a plugin to publish configurations exclusively for use by itself, so there is no isolation.
Using the newer Capabilities functionality allows for this isolation to be better established.