gradle-aem-plugin
gradle-aem-plugin copied to clipboard
wttech
Swiss army knife for Adobe Experience Manager related automation. Environment setup & incremental AEM application build which takes seconds, not minutes.
imagine, instead of embedding ``` packageCompose { installBundle("org.hashids:hashids:1.0.3") { wrap { exportPackage("org.hashids.*") } } } ``` then adding regular `dependencies { compileOnly("org.hashids:hashids:1.0.3") }` somewhere and voila. implementation: resolving dependency, extracting...
imagine RMC on file/folder, then "GAP / Sync" which will run sync with `:aem:site.demo:sync -Pfilter.roots=[path]` reflects other plugin functionalities, however GAP offers much more than content downloading but also also...
by integrating oakrun tool in #812 it will open a possibility to also use oakrun to compact the size of AEM repository. doing it by simply running the task `instanceCompact`...
Task `instanceUp` is saving e.g JAVA\_EXECUTABLE absolute path in `control/\*.\[bat|sh]` scripts and it makes instances not usable directly when extracted externally (outside of GAP usage). Consider passing user-specific data to...
When some instance details are changed or instance files updated, then instance should be turned off then on again. This feature should address cases like changing run mode, adding some...
When running `instanceUp` task then at first `instanceCreate` is called. Both tasks are running the method LocalInstance.customize() which is applying configuration changes from gradle.properties like aem run modes, admin password...
To clean up repository / reduce size Inspired by: https://medium.com/vrt-digital-studio/13-steps-to-rock-stable-aem-package-installs-d9bbba1f7b15 - "Clean up the previous versions" maybe introducing new task `instanceClean` ?
https://github.com/Cognifide/gradle-aem-plugin/blob/master/src/asset/localInstance/defaults/service/systemd.conf by default is `oneshot`, but `forking` seems to be better, however there are more constraints like https://askubuntu.com/questions/1044464/new-main-pid-does-not-belong-to-service-and-pid-file-is-not-owned-by-root when `User=` is set (when AEM is running as root, the issue...