This message was deleted.
# community-support
s
This message was deleted.
v
I'm not sure what you mean. If you mean you want to add a classifier to a version catalog then no, that's out of scope of the version catalog. If you mean to specify the classifier where the version catalog accessor is used, then yes.
c
Either or? How would you add the classifier where it's used?
v
Copy code
implementation(libs.yourlib) {
    artifact {
        classifier = "whatever"
    }
}
👍 1
c
Thanks
👌 1
Does that work on a plug-in? Via alias?
v
I don't think a classifier makes sense in case of a plugin?
c
Oh you're right... I'm tired I've worked way too many hours this week. I'm thinking of an annotation processor thing, which quite often comes with plugins. In this case kapt
v
The alias is an alias for the id which resolves to the marker artifact which resolves to the code artifact. If you need something with classifier (which you shouldn't) you probably use the legacy way using dependency in the buildscript block and there you have the same syntax available
c
Yeah, no it's just a library I pass to kapt