Reference aem-sdk-api with scope "import"


In the aem-sdk-api is not referenced with scope import but compile. That limits the managed versions to the aem-sdk-api itself but not its transitive dependencies.


Stefan Seifert
October 8, 2020, 10:03 AM

closing this until there is an AEM SDK API POM with transitive dependencies

Stefan Seifert
August 19, 2020, 8:34 AM

i compared the output of "help:effective-pom" with and without your PR and the OSGi deps only got removed, but nothing added by the import. did not try it out in a real project, though.

the versions for the various OSGi and sling annotations we usually do not define in the aem-dependencies/aem-cloud-dependencies POM but within the aem-global-parent POM
as those versions are not directly related to the underlying AEM version, but more to the versions of the related plugins defined in aem-global-parent (like bnd maven plugin plugin and it's dependencies).

Konrad Windszus
August 19, 2020, 8:28 AM

Hi Stefan,

I tried it out with Maven 3.6.2 and with this PR I had no longer give a version for


But indeed as aem-sdk-api does not have any dependencyManagement it should not have any effect, I need to figure out what is going on in;a=blob;f=maven-model-builder/src/main/java/org/apache/maven/model/composition/;h=d895913eb6b665193da46e965f48f7fffefcde1c;hb=HEAD.



osgi.cmpn is not included in aem-sdk-api

Indeed only osgi.core is defined there.

Stefan Seifert
August 19, 2020, 8:04 AM

related PR is:

thanks - however, this does not work:

  1. import scope does only work for dependencies defined in the dependencyManagement section of the target POM - but the aem-sdk-api defines only direct dependencies

  2. osgi.cmpn is not included in aem-sdk-api

Konrad Windszus
August 17, 2020, 5:25 PM




Konrad Windszus