change the maven-enforcer-plugin rule for java-version to require version 11 instead of 1.8
create a it-java8 profile that changes the archetype.test.projectsDirectory when executed with jdk 1.8 to point to a new sibling folder projects-1_8 containing symbolic links to non-cloud IT project directories, so that the archetype project itself continues to build successfully for both jdk1.8 and jdk11 executions.
Related Issue
ASSETS-35923 Release 15262 aem-sdk-api breaks the sample unit tests in aem-project-archetype projects when running under JDK8, including new sandbox programs
Motivation and Context
Upstream project dependencies of AEM are gradually moving to Java 11+ targets, which are compatible with the AEM Cloud Service runtime, but not compatible with the default Cloud Manager JDK version 1.8. Until the minimum supported version of AEM on AMS/On-Prem is raised above 1.8, the archetype should extend its conditional logic for cloud vs non-cloud to govern the required JDK version as well, so that cloud projects and the cloud SDK can evolve more cohesively.
How Has This Been Tested?
Executed the archetype locally under jdk 1.8 and jdk 11 to confirm that the tests pass and that the aemVersion=cloud IT projects contain a .cloudmanager/java-version file with the contents 11 and that they fail early if they are built with jdk 1.8.
Screenshots (if appropriate):
Types of changes
[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
Projects created for cloud should be expected to build with a minimum jdk version of 11.
Description
.cloudmanager/java-version
for cloud projects with text content11
, per Setting the Maven JDK Versionit-java8
profile that changes thearchetype.test.projectsDirectory
when executed with jdk 1.8 to point to a new sibling folderprojects-1_8
containing symbolic links to non-cloud IT project directories, so that the archetype project itself continues to build successfully for both jdk1.8 and jdk11 executions.Related Issue
ASSETS-35923 Release 15262 aem-sdk-api breaks the sample unit tests in aem-project-archetype projects when running under JDK8, including new sandbox programs
Motivation and Context
Upstream project dependencies of AEM are gradually moving to Java 11+ targets, which are compatible with the AEM Cloud Service runtime, but not compatible with the default Cloud Manager JDK version 1.8. Until the minimum supported version of AEM on AMS/On-Prem is raised above 1.8, the archetype should extend its conditional logic for cloud vs non-cloud to govern the required JDK version as well, so that cloud projects and the cloud SDK can evolve more cohesively.
How Has This Been Tested?
Executed the archetype locally under jdk 1.8 and jdk 11 to confirm that the tests pass and that the aemVersion=cloud IT projects contain a
.cloudmanager/java-version
file with the contents11
and that they fail early if they are built with jdk 1.8.Screenshots (if appropriate):
Types of changes
Checklist: