With the commit https://fisheye6.atlassian.com/changelog/sling?cs=1767036
ResourceResolver was migrated from SCR to OSGi component/metatype annotations.
This looks really nice and clean except for the ID of the attribute entry is
always(!) generated from the annotated method name, which leads to weird method
names like resource_resolver_searchpath() (which is converted to id
resource.resolver.searchpath, according to
https://osgi.org/javadoc/r6/enterprise/org/osgi/service/metatype/annotations/AttributeDefinition.html).
Is there really no way to decouple the generated ID from the method name? I
would have expected that it is possible to override the id by some attribute on
the annotation @AttributeDefinition.
Would it be worth to consider that for the next update to metatype spec?
Thanks,
Konrad
