Core Component issue

[Punitha77]

When I install the project using maven command and tried to add a component in the page. It is blank 

Maven command

mvn -B org.apache.maven.plugins:maven-archetype-plugin:3.2.1:generate -D archetypeGroupId=com.adobe.aem -D archetypeArtifactId=aem-project-archetype -D archetype Version=39 -D appTitle="Modern Creator" -D appId="moderncreator" -D groupId="com.modern.creator" -D aemVersion=6.5.13 -D singleCountry=n

Core Component Details

Symbolic Name	com.adobe.cq.core.wcm.components.core
Version	2.19.0

Error

In system console I could see the core bundle is in installed state.

Imported Packages

com.day.cq.wcm.api,version=[1.29,2) -- Cannot be resolved org.apache.sling.api.resource,version=[2.12,3) -- Cannot be resolved org.apache.sling.api.servlets,version=[2.3,3) -- Cannot be resolved

[Mahesh_Gunaje]

Hi @Punitha77 

Go to localhost:4502/welcome  check the AEM version.

go to localhost:4502/system/console/bundles.  check the core.wcm version. this should be proper one. if possible, add the error.log file content here.

[Kamal_Kishor]

@Punitha77 : Please refer this to see for the bundle errors you are seeing:

https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/com-day-cq-wcm-api-cannot-...

thanks.

[arunpatidar]

Hi @Punitha77 
Please check the compatibility here :

https://github.com/adobe/aem-core-wcm-components/blob/main/VERSIONS.md 

[partyush]

Hi @Punitha77 

The issues you're facing seem to be related to incompatible package versions within your AEM project. Here's a breakdown of the problem and steps to fix it:

Problem:

1. Missing Dependencies: Your Core Component ("com.adobe.cq.core.wcm.components.core") version (2.19.0) requires specific versions of certain packages that are not present or incompatible with your project.
2. Incompatible Package Versions: The error message in the System Console points out missing or incompatible versions of com.day.cq.wcm.api, org.apache.sling.api.resource, and org.apache.sling.api.servlets.

Solution:

1. Verify Dependencies: Check the dependencies of your Core Component in the JCR repository (e.g., using CRXDE Lite) or refer to the component's documentation.
2. Update Dependencies: Make sure your project's pom.xml file includes dependencies for the required packages with compatible versions.
3. Use Dependency Management: Leverage Maven dependency management tools like dependencyManagement or dependencyConflictId in your pom.xml to handle conflicting versions effectively.
4. Clean Maven Cache: Sometimes, the issue might be due to a stale Maven cache. Try running mvn clean install before deploying your project again.

I Hope this helps.

Thanks 

[kautuk_sahni]

@Punitha77 Did you find the suggestions from users helpful? Please let us know if more information is required. Otherwise, please mark the answer as correct for posterity. If you have found out solution yourself, please share it with the community.

[Sudheer_Sundalam · Accepted solution]

@Punitha77 ,

Please install AEM Service Package 13 or above on the author/publish instance where you are trying to build and install this code.

[Punitha_s]

It helped!!

Thank you @Sudheer_Sundalam 

[TarunKumar]

Hi @Punitha77 ,

Can you please check if your uber jar version is compatible with the AEM instance version also make sure you have service pack 13 installed in your AEM.

Once the above check id one then  try to restart the lower environments - http://localhost:4502/system/console/vmstat#

Thanks
Tarun

[Punitha_s]

I have installed service package and it helped and when try to restart the lower environments - http://localhost:4502/system/console/vmstat# it crashed

Thanks @TarunKumar 

Regards,

Punitha

[TarunKumar]

Hi @Punitha_s ,

Usually it takes 5-10 min for server to start and keep running once the service pack is installed.

[kautuk_sahni]

@Punitha77 Do the recommendations provided by the community members prove useful for you? Alternatively, if you've resolved this yourself, could you share the details with the community for posterity?