Hi All,
Can any one provide me solution to resolve the following :
Here I am using AEM 6.5 still I am using the latest Uberjar eventhen I am getting this issue
Thanks,
Pavan
Solved! Go to Solution.
Views
Replies
Total Likes
Hi @Adobe_CQ_Dispat,
Can you let know if AEM 6.5 is a fresh install type or in-place upgraded instance?
Cross check
If everything looks fine and still an issue, try to restart the framework if it is your local or any lower environments - http://localhost:4502/system/console/vmstat
Is this issue happening in your local environment ?
Do you see any error in logs?, can you provide error log trace.
Hi @Adobe_CQ_Dispat,
Can you let know if AEM 6.5 is a fresh install type or in-place upgraded instance?
Cross check
If everything looks fine and still an issue, try to restart the framework if it is your local or any lower environments - http://localhost:4502/system/console/vmstat
Hi @Shivam_S,
If you have created project using AEM Maven Archetype, you would have this dependency entry available by default in main pom.xml and in core/pom.xml (with just the groupId and artifactId entry)
<dependency>
<groupId>com.adobe.aem</groupId>
<artifactId>uber-jar</artifactId>
<version>6.5.0</version>
<classifier>apis</classifier>
<scope>provided</scope>
</dependency>
Use this WKND project code base from this GitHub location - https://github.com/adobe/aem-guides-wknd
If you could see here <uber.jar.version> is available as properties in main/pom.xml - You can specify the desired AEM version.
The same is used in core/pom.xml for the artifactId, uber-jar
* Is your uber jar version compatible with the exact version of your AEM 6.5 that you are using?
Example:
AEM: 6.x.y
Uber Jar: uber-jar-6.x.y-apis.jar
or
uber-jar-6.x.y-apis-with-deprecations.jar
Found another community article that might be helpful:
Views
Likes
Replies