Hi Community,
I created a new project from scratch based on the latest archetype, but it loads blank after trying to load the home page.
It is important to mention all bundles are up and running all dependencies are OK, the only log messages I get are the following.
================================================================================================
Solved! Go to Solution.
Views
Replies
Total Likes
Hi,
I think there should be something else in the log to indicate what's going on. I just used the archetype 51, as you mentioned, to generate a project and deploy it into my local SDK Version 2024.10.18311.20241017T104455Z, and it worked without any problems.
mvn -B org.apache.maven.plugins:maven-archetype-plugin:3.2.1:generate \
-D archetypeGroupId=com.adobe.aem \
-D archetypeArtifactId=aem-project-archetype \
-D archetypeVersion=51\
-D appTitle="My Site" \
-D appId="mysite" \
-D groupId="com.mysite"
Here are a few things to check:
Ensure you are deploying to the correct version (AEM Cloud to a valid SDK version, and On-Premise to an on-premise AEM instance).
In my opinion, the logs should point to something else. Please double-check and see if you find anything, and post it back.
Try installing the same project on a fresh AEM instance.
Hope this helps
@EstebanBustamante @SureshDhulipudi @Jörg_Hoh @h_kataria would you please take a moment to review this question? We would be grateful if you could share your suggestion on this question.
Views
Replies
Total Likes
Hi,
I think there should be something else in the log to indicate what's going on. I just used the archetype 51, as you mentioned, to generate a project and deploy it into my local SDK Version 2024.10.18311.20241017T104455Z, and it worked without any problems.
mvn -B org.apache.maven.plugins:maven-archetype-plugin:3.2.1:generate \
-D archetypeGroupId=com.adobe.aem \
-D archetypeArtifactId=aem-project-archetype \
-D archetypeVersion=51\
-D appTitle="My Site" \
-D appId="mysite" \
-D groupId="com.mysite"
Here are a few things to check:
Ensure you are deploying to the correct version (AEM Cloud to a valid SDK version, and On-Premise to an on-premise AEM instance).
In my opinion, the logs should point to something else. Please double-check and see if you find anything, and post it back.
Try installing the same project on a fresh AEM instance.
Hope this helps
Views
Likes
Replies
Views
Likes
Replies