Some dependencies are older versions because of the back end code. Which dependency should I be looking at to resolve this? If you have an idea which dependencies I need to look at, that would help. The problem I'm having is that I don't know which one is causing the issue.

I think people are a little confused. Our code uses none of the core components in AEM 6.5. They are all classic UI based so I see no point in chasing down core component dependencies. There are none.I am fully aware that the classic UI is deprecated and not supported. That being said, if you really...

I've noticed this line in the bundle manifest header when looking at the details in the OSGI bundle page.Require-Capability: osgi.extender; filter:="(&(osgi.extender=osgi.component)(version>=1.5.0)(!(version>=2.0.0)))", osgi.ee; filter:="(&(osgi.ee=JavaSE)(version=1.8))"This is not in my pom.xml fil...

Actually, AEM 6.5 does support the classic UI components. However they are deprecated and not being supported but they do still work. I have seen it in action and know this for a fact. I don't think the core components would really have any effect on this because they are now all touch UI and our co...

acs-aem-commons-all.6.0.10, aem-service-pkg.6.5.15 have been applied.

As stated above, 6.5.15 with patches and updates.

This maven project is for building our customizations. It is a port from 6.2 and we haven't converted the classic UI components over to touch UI yet. That may happen next year. I'm trying to simplify the build/deploy process so that fewer mistakes are made when developers try to build and deploy the...

AEM 6.5.15

I am working on an update from a very old archetype to a newer AEM Archetype version 41 and I am having a binding issue after the bundle is deployed to the localhost instance.The error I'm seeing when I attempt to start the bundle is as follows:29.11.2023 09:19:09.646 *ERROR* [qtp693971857-5631] org...

This just keeps getting stranger. I still haven't found a resolution to this. I added code to get the class object of the currentPage attribute in the JspContext..From the logs:The class is com.day.cq.wcm.core.impl.page.PageImplInterface0 = com.day.cq.wcm.api.PageSuper Class = org.apache.sling.adapt...