Implemented support for external console extensions

markdaugherty commented 9 years ago

Since the binding and star imports extensions are specific to Groovy script execution, I moved these services into the Groovy Console project.
I updated the method signature for the metaclass extension service so the map value is a single closure rather than an array of closures; my thought is that any implementation of this service will only map a single metaclass closure to a given class. The "aggregator" service (com.citytechinc.aem.groovy.extension.services.impl.DefaultExtensionService) will then handle registration of these metaclasses for each implementation.
Other changes were minor, mainly naming and cleanup for consistency.

markdaugherty commented 9 years ago

Can you review the updates and ensure that it still works for all of your use cases? If so, I can proceed with the 0.7.1 release for CQ 5.6 and also merge this forward for the current development branch.

CptBartender commented 9 years ago

These changes work for me, I don't see anything working not as expected. Same with the console project.

markdaugherty commented 9 years ago

FYI, this has also been merged into release 0.9.0 and the develop branch for whenever you get around to upgrading to AEM 6. :-)

icfnext / aem-groovy-extension

Implemented support for external console extensions #3