Hi All, Recently we had VM migration from an old location to another one. The migration cloned one branch of the whole architecture as the following: author -> publisher -> dispatcher. Nothing changes except the new clone has a new domain name. Now we found a problem, the dispatcher doesn't cache. W...

Thanks for your advice, it's really helpful. I am actually doing mostly as you are advising. It's impossible to copy and paste as I am looking deeper into the two different versions.

Do we have to follow Adobe's Archtype13 structure, or just keep the old if considering the easy way at the first step? Moving to new structure invites a lot of challenges such as package names, dependencies. But I am afraid keeping the old structure will not be compatible with 6.5.

Thank you! Yes, we are considering moving to CoralUI. Another challenge is we need to change all jsp, jstl to htl also.

Thanks for your advice, it's really helpful

Hi all, Wish everyone to stay well during this difficult time.We are considering to upgrade from 6.0 with sp3 to 6.5. I read through this article and it doesn't look like we need to run the repo conversion jar. The most difficult thing is the code migration. The structure is very different and it se...

I built the bundle successfully anyway. Probably the Eclipse is not configured to import the appropriate packages. This happened to my 6.0 also.

Hi All,We've been building AEM 6.0 bundles using the old archetype and it looks like a lot of changes moving to AEM 6.4. I followed all the instructions as described in this page: Creating an Adobe Experience Manager 6.4 Project using Adobe Maven Archetype 13 Here's what I've done:- I created a sett...

It's installing the jar file, but not loading the updated one. I tried a few times to upload it from the package manager and installed it on different servers, all other servers are the same. I barely remember if it was working without restarting the server, seems that it changed to the current beha...

Yes, tried multiple times, but it doesn't help.