This message was deleted.
# dependency-managements
Slackbot
09/14/2022, 6:00 PMThis message was deleted.
🙌 1
🧵 1
c
Chris
09/14/2022, 6:07 PMSounds like you want the third-parties to apply a plugin that publishes a new variant with a some custom attributes defined by your plugin… then you have a resolvable configuration in your consuming project that requests those attributes.
e
efemoney
09/14/2022, 6:31 PMyeah exactly. within my own build logic, how can I configure my build that for any dependency added in
implementationa:b:cmyMetadatac
Chris
09/14/2022, 6:32 PMyou create a resolvable configuration that extends implementation and requires that attribute
Chris
09/14/2022, 6:33 PMyou may then need a artifact view or a lenient configuration to resolve it since you know some artifacts will not have a matching variant
Chris
09/14/2022, 6:35 PMI find
JvmPluginServices Copy code
Configuration myMetadata = jvmPluginServices.createResolvableConfiguration("myMetadata", builder -> builder
.extendsFrom(implementation).requiresAttributes(attrs-> attrs...))party gradlephant 1
til 1
e
efemoney
09/14/2022, 7:34 PMThank you!
efemoney
09/14/2022, 7:35 PMOkay, now for level 2 difficulty, what if, the custom configuration that I want to funnel that variant into is not created by me 😅 but another plugin and per-adventure it doesnt extend implementation 😅
n
Niels Doucet
09/15/2022, 7:44 AMyou can make it extend implementation
👍 1