Currently, we are in 6.4.2, and we are adding a new repo to the instance. We are planning for the AEM instance upgrade to 6.4.6 or .8 in the future( not yet decided for timeline). After building the project, we intended to all core components( because every archetype tied with diff versions- archetype 22 comes with 2.7.0 and my env using 2.5.0) dependencies from the code.
when i compare 2 pom.xml's, archetype 22 is creating extra all folder in the structure and below are the few differences present in remaining pom.xml files-
<plugin> <groupId>biz.aQute.bnd</groupId> <artifactId>bnd-maven-plugin</artifactId> <version>${bnd.version}</version> </plugin> <dependencies> <dependency> <groupId>org.apache.sling</groupId> <artifactId>org.apache.sling.caconfig.bnd-plugin</artifactId> <version>1.0.2</version> </dependency> </dependencies> <dependency> <groupId>javax.annotation</groupId> <artifactId>javax.annotation-api</artifactId> </dependency>
Can we use archetype 22?
Solved! Go to Solution.
Views
Replies
Total Likes
Hi @ramaem12,
The Maven Archetype version has very little to do with the AEM version. The only critical elements are:
Here are the requirements for the 22 version:
Requirements
The latest version of the archetype has the following requirements:
Hi @ramaem12,
The Maven Archetype version has very little to do with the AEM version. The only critical elements are:
Here are the requirements for the 22 version:
Requirements
The latest version of the archetype has the following requirements:
To be on the safe side you can see a list of supported AEM versions of historical archetype versions:
https://github.com/adobe/aem-project-archetype/blob/master/VERSIONS.md
Views
Replies
Total Likes
Views
Replies
Total Likes
Views
Likes
Replies