-
Notifications
You must be signed in to change notification settings - Fork 428
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AEMaaCS SDK and archetype compatibility #1043
Comments
There is a mvn shell script located in bin directory of Dispatcher SDK tooling which updates immutable files in your local pointed directory to the one from the SDK and patches your pom.xml to match their checksums. |
ok, so from time to time this script need to be launched to keep things synchronised. fair enough. thanks for clarifying this |
Resolved with #1045 from Dispatcher SDK tooling version 2.0.166 - to be available in Archetype 41 (next to be released) |
According to "Cloud-Ready" mentioned here: https://experienceleague.adobe.com/docs/experience-manager-core-components/using/developing/archetype/overview.html I see "continual" at the system requirements...
Is it somewhere stated which exact archetype version is compatible with which SDK version? I was expecting that the recent SDK would be consistent with the current archetype but unfortunately seems that not.
I just started playing with the recent AEMaaCS SDK - aem-sdk-2023.1.10912 and generating project from archetype 40 recently released however I spotted that the dispatcher validator complains that immutable dispatcher config files generated from archetype are changed ;/
Archetype needs to be aligned, I suppose?
Greetings, Krystian
The text was updated successfully, but these errors were encountered: