Hi @shivparekh21 ,
It looks like you're encountering dependency resolution issues when building the WKND project in AEM 6.5 using Maven. These errors indicate that certain OSGi dependencies are not being resolved during the build process.
Here are the steps to troubleshoot and resolve these issues:
1. Check Dependencies and Repositories
Ensure that the pom.xml of your project contains the correct dependencies and repositories for resolving the required bundles.
a. Verify Repositories
Make sure you have the following repositories configured in your pom.xml:
<repositories>
<repository>
<id>adobe-public-releases</id>
<url>https://repo.adobe.com/nexus/content/groups/public/</url>
</repository>
<repository>
<id>central</id>
<url>https://repo.maven.apache.org/maven2</url>
</repository>
</repositories>
b. Verify Dependencies
Ensure that the dependencies for the required packages are listed in your core/pom.xml or all/pom.xml:
<dependencies>
<!-- Example dependencies, adjust versions as needed -->
<dependency>
<groupId>com.adobe.aem</groupId>
<artifactId>aem-sdk-api</artifactId>
<version>2021.10.5455.20211012T100432Z-210900</version>
<scope>provided</scope>
</dependency>
<dependency>
<groupId>com.adobe.cq</groupId>
<artifactId>cq-wcm-api</artifactId>
<version>6.5.0</version>
<scope>provided</scope>
</dependency>
<dependency>
<groupId>com.fasterxml.jackson.core</groupId>
<artifactId>jackson-core</artifactId>
<version>2.11.3</version>
</dependency>
<!-- Add other required dependencies similarly -->
</dependencies>
2. Ensure Proper Maven Profiles
Ensure that you are using the correct Maven profiles during the build. For AEM 6.5, the classic profile should be sufficient, but you might need to adjust the build profiles.
mvn clean install -PautoInstallSinglePackage -Pclassic
3. Verify OSGi Bundle Versions
Check if the specific versions of the required OSGi bundles are available in the Adobe repository. If they are not, you might need to adjust the versions in your pom.xml.
4. Update and Synchronize Dependencies
Sometimes, updating the project and synchronizing dependencies can resolve version conflicts:
mvn clean install -U
5. Check AEM Instance and Logs
- Ensure your AEM instance (Author/Publish) is running and accessible.
- Check the AEM error logs (/crx-quickstart/logs/error.log) for any deployment or runtime issues.
Example core/pom.xml Configuration
Here’s an example configuration snippet for core/pom.xml:
<project>
<!-- Other configurations -->
<dependencies>
<dependency>
<groupId>com.adobe.aem</groupId>
<artifactId>aem-sdk-api</artifactId>
<version>2021.10.5455.20211012T100432Z-210900</version>
<scope>provided</scope>
</dependency>
<dependency>
<groupId>com.adobe.cq</groupId>
<artifactId>cq-wcm-api</artifactId>
<version>6.5.0</version>
<scope>provided</scope>
</dependency>
<dependency>
<groupId>com.fasterxml.jackson.core</groupId>
<artifactId>jackson-core</artifactId>
<version>2.11.3</version>
</dependency>
<!-- Add other dependencies similarly -->
</dependencies>
<repositories>
<repository>
<id>adobe-public-releases</id>
<url>https://repo.adobe.com/nexus/content/groups/public/</url>
</repository>
<repository>
<id>central</id>
<url>https://repo.maven.apache.org/maven2</url>
</repository>
</repositories>
<!-- Other configurations -->
</project>
Conclusion
By ensuring that the correct dependencies and repositories are configured in your pom.xml files, you should be able to resolve the issues with missing packages and OSGi dependencies. If problems persist, review the error logs for more specific details on the root cause and adjust your project configuration accordingly.
