To keep the classpath lean it is often beneficial to reference the individual artifacts instead of the aggregates like core or cmpn. For a discussion around that see https://issues.apache.org/jira/browse/SLING-7384?focusedCommentId=16327433&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16327433. It would be nice if those dependencies were managed in https://github.com/wcm-io/wcm-io-tooling-aem-cloud-dependencies as well.
Compare also with the related ticket https://github.com/adobe/aem-project-archetype/issues/182.
thanks, i've added the individual artifacts as alternative
deriving the spec version from the package versions of the related bundles works well - except the felix converter bundle, which exports package versions for org.osgi.util.converter which are not related to the spec version (strange).
the individual artifacts will also be part of the AEM 6.5.5/6.5.6 deps POMs.
Thanks Stefan, what about the annotations (ds, metatype, version, bundle)?
they are part of our "aem-global-parent" POM
as they are not closely attached to the running AEM version, but to the versions of the other build-related plugins (e.g. bnd maven plugin version) and the declared bnd plugins.
Very often usage of new annotations can lead to runtime dependencies with newer osgi packages, therefore I recommend to e.g. only use component annotations 1.4 in case DS 1.4 is available. Compare also with
alright, i've added the annotation artifacts as well - maybe we will phase them out in aem-global-parent later