adobe / adobe/aemanalyser-maven-plugin
analyse error: Artifact requires [aem-guides-wknd.core/0.0.6] osgi.ee; filter:="(&(osgi.ee=JavaSE)(version=11))" when compiled with Java 8
- Dominant language
- Java
- Stars
- 30
- Forks
- 25
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 2
Description
When you execute `mvn verify` on https://github.com/kwin/aem-analyser-example/tree/analyse-failure-with-java8 with Java 8 you get
```
[ERROR] com.adobe.aem.guides:aem-guides-wknd.core:0.0.6: Artifact com.adobe.aem.guides:aem-guides-wknd.core:0.0.6 requires [aem-guides-wknd.core/0.0.6] osgi.ee; filter:="(&(osgi.ee=JavaSE)(version=11))" in start level 20 but no artifact is providing a matching capability in this start level.
[ERROR] Analyser detected errors on feature 'biz.netcentric.aem:aem-analyser-example:slingosgifeature:aggregated-author.prod:0.0.1-SNAPSHOT'. See log output for error messages.
```
No error is emitted with Java 11! The capability version of osgi.ee should not be derived from Java version of the Maven build but rather from the Java version AEM is running with (always 11 for AEMaaCS).
Contributor guide
Research direction
Start by checking out the analyse-failure-with-java8 branch and running mvn verify with Java 8, then compare the result with Java 11. Trace how the analyser determines the osgi.ee capability for the aggregated feature; done means Java 8 builds use the Java 11 capability expected by AEM as a Cloud Service without emitting this error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100