Unresolved compilation problem about aem-groovy-console HOT 5 CLOSED

Is the groovy-all bundle started and running on author? Outside of more rare/unusual OSGi container issues, the typical cause for unresolved Groovy classes is a missing or not-running bundle.

from aem-groovy-console.

Hey,

Jup, all the bundles are running

Greets,
Roy

from aem-groovy-console.

OK, now we're getting into more obscure causes... let me get an SP2 instance running and see if I can replicate your issue. Thanks for your patience!

from aem-groovy-console.

Hey @lykorian,

Thanks! Just to make sure that you have all the info ;) this is an updated AEM from AEM 5.6.1 which used to have the groovy console version 5 running on it. I am not sure if that has anything to do with it though, seeing as it did work for a while after the upgrade..

Greets,
Roy

from aem-groovy-console.

@royteeuwen I vaguely recall running into similar issues when we upgraded the console from 5.. to 8+ on one of my projects.

IIRC that had to do with the fact that the CRX Package name changed between versions, from cq-groovy-console to aem-groovy-console so simply uploading the new package and installing it did not update the old version. It was treated as a separate package, not a new version of the same thing.

Make sure version 5 is properly uninstalled. Remove the contents of /etc/groovyconsole as well as the CRX Package and the OSGi bundles (it's possible you still have the old ones running).

Check /var/classes for potentially cached JSPs and wipe them out as well.

After a thorough cleanup of the old version, restarting the instance and installing the new console, it started working for me.

from aem-groovy-console.