Hi All,
I'm working on aem 6.3 to 6.5 in place upgrade activity. After running pattern detector I have found the below issue:
Can anyone help me resolve this.
Thanks
Solved! Go to Solution.
Views
Replies
Total Likes
Hello,
This means that the bundle mentioned has a dependency which will no longer be available when you upgrade to 6.5, so it won't work anymore.
The screenshot is very small but if I'm not mistaken you got this warning for a bundle that is part ACS Commons, correct? What version are you using?
If you look at the compatibility matrix, you will see that you need to be on version 4.x.x minimum for AEM 6.5 (which is also compatible with AEM 6.3). If you update ACS Commons to 4.5.0, the issue should be fixed
Hello,
This means that the bundle mentioned has a dependency which will no longer be available when you upgrade to 6.5, so it won't work anymore.
The screenshot is very small but if I'm not mistaken you got this warning for a bundle that is part ACS Commons, correct? What version are you using?
If you look at the compatibility matrix, you will see that you need to be on version 4.x.x minimum for AEM 6.5 (which is also compatible with AEM 6.3). If you update ACS Commons to 4.5.0, the issue should be fixed
Views
Replies
Total Likes
No worries, I was on my phone and it didn't let me zoom in. Here on PC it's okay.
I see now hat it is ACS Tools and not ACS Commons that is causing the issue.
Good news:
I've just intalled ACS Tools 1.0.2 on a 6.5 instance and although I haven't tested all the features, it seems to work okay (despite one bundle not starting).
Bad news:
Judging be the GitHub repo, ACS Tools hasn't been updated since December 2018. AEM 6.5 came out in April 2019, so it's no surprise that that there might be some issues!
Conclusion:
It is clearly stated on the ACS Tools page: "ACS AEM Tools is ONLY for use on development and QA environments.". So on one hand it's outdated and potentially a security risk, but on the other hand if you only use it in your DEV environment, its probably fine... However, in order to keep your instance as lean and clean as possible, a 6.3 -> 6.5 migration is a good time to ask yourself if you really need those features. If not, you should remove them as it will make your life easier
Views
Replies
Total Likes