I have about 20 annotations that need to be exactly like that but I want to avoid code duplication

paulwoitaschek: but… why? 😱

Because code duplication is bad?

some frameworks support meta annotations, i.e. you write

@Qualifier
@Target(AnnotationTarget.PROPERTY, AnnotationTarget.FUNCTION)
@Retention(AnnotationRetention.RUNTIME)
annotation class MetaAnn

@MetaAnn
annotation class Something

@Paul Woitaschek no, I meant why have 20 annotations

I'm injecting perference classes of different types and I need qualifiers so my DI framework knows where each one has to go

sounds like too much work to me 😉

How would you inject the preferences with less work?

I probably wouldn’t inject them at all, but I don’t know your use case or your app, so I’m sure that it’s the best solution in your case.

DI frameworks often support some kind of named or tagged bindings. Maybe that would work for you?

I like it that way. I want to inject them for testing, that's easier. And once I set up these qualifiers, it's real clear code