I am trying to set up a project using the command of " mvn -B archetype:generate -D archetypeGroupId=com.adobe.aem -D archetypeArtifactId=aem-project-archetype -D archetypeVersion=39 -D appTitle="AEM Bootcamp Site" -D appId="aem-bootcamp" -D groupId="com.aembootcamp" -D frontendModule="general" -D includeExamples=n -D includeErrorHandler=n -D amp=n -D includeDispatcherConfig=n -D aemVersion=6.5.14 ". Now in cmd i am using mvn clean install for setup but it raised error in core module.
Solved! Go to Solution.
Views
Replies
Total Likes
Hi @MeghanaPa
You need to use some other version than 6.5.14, the specified version Uber-jar is not available in maven central. try using 6.513 or 6.5.15 instead.
Not resolved still same error.
Please try with command
mvn clean install -U -e -PautoInstallPackage,adobe-public
@MeghanaPa , In your project pom find the below dependency and update the version from 6.5.14 to 6.5.13.
<dependency>
<groupId>com.adobe.aem</groupId>
<artifactId>uber-jar</artifactId>
<version>6.5.14</version> <!-- Uber version update to SP 6.5.13 -->
<scope>provided</scope>
</dependency>
Hope this helps!!
Both the archetype and AEM versions are old. Are you sure you need these, especially considering you are creating a new project?
Hi @MeghanaPa , there is no dedicated uber-jar with version 6.5.14. Try to use 6.5.13 instead.
Please refer more information here https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/when-will-uber-jar-6-5-14-...
Hi @MeghanaPa
You need to use some other version than 6.5.14, the specified version Uber-jar is not available in maven central. try using 6.513 or 6.5.15 instead.
Hi @MeghanaPa ,
It seems like there might be an issue with your AEM project setup or with the code in your core module. Let's troubleshoot this step by step:
Check the Error Message: The error message you provided, "AEM Bootcamp Site - Core ........................... FAILURE [ 0.780 s]", indicates that there's a failure during the build process of the core module. We need to find out what specific error is occurring.
Look into Core Module: Navigate to the core module of your project and examine the error messages printed during the build process. These messages will provide more details about what went wrong. It could be a compilation error, dependency issue, or something else.
Check Logs and Stack Trace: Look for any stack trace or error logs generated during the build process. They often provide valuable insights into the root cause of the problem.
Inspect POM Files: Check the pom.xml files in your project, especially in the core module. Make sure all dependencies are correctly defined and versions are compatible with each other and with your AEM version (6.5.14 in this case).
Review Configuration: Ensure that your project setup matches your AEM version (6.5.14) and that all configurations are correct. Sometimes errors can occur due to misconfiguration.
Check Java Version: Make sure you're using a compatible Java version with AEM 6.5. AEM 6.5 is compatible with Java 11. Ensure that your JAVA_HOME environment variable points to the correct Java 11 installation.
Update Dependencies: If you recently updated your AEM version or any dependencies, ensure that they are compatible with each other. Sometimes conflicts between dependencies can cause build failures.
Search Online Forums: If you're unable to identify the issue, try searching online forums or communities like Stack Overflow. Others might have encountered similar issues and found solutions.
Thanks!
@MeghanaPa 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.
Views
Replies
Total Likes
Views
Likes
Replies