Closed royteeuwen closed 1 year ago
Better to put "gdsl" file inside some jar file in "aem-easy-content-upgrade" project then groovy editor will take definitions from that file automactically from maven dependencies.
For example "aecu.gdsl" in resources folder in api bundle
def aecuCtx = context(scope: scriptScope(), scriptType: 'aemconsole')
contributor(aecuCtx) {
field name: 'aecu', type: 'de.valtech.aecu.api.groovy.console.bindings.AecuBinding'
}
@bobi thanks for adding the support into the plugin! I was still planning to do the gdsl, just didnt get around to it yet :(,
We use aem easy content upgrade as framework to do our automated migrations. It would be nice if you could add extra custom bindings (or support aecu) to the AEM Groovy Console Plugin:
For your information, it creates a binding named
aecu
in your groovy scripts, see: https://github.com/valtech/aem-easy-content-upgrade