Open leojplin opened 8 years ago
Agreed: Having a samples area would probably be useful.
+1
or even better, provide a skeleton as separate project which can be easily cloned and reused. I am tryining to migrate from mvn but without docs it's quite painful :>
In the mean time, the test cases show explicitly how everything is expected to be used, in particular CqPackagePluginIntSpec creates stub projects and associated build files.
A good way to solve this would be gradle fork plugin: https://github.com/neva-dev/gradle-fork-plugin
It's used by quick starts for gradle-aem plugin: https://github.com/Cognifide/gradle-aem-plugin#installation
Hi,
I am new to using gradle, but I am very interested in gradle. And thanks for writing plugins for AEM, as it is my job to work on AEM. It would be really nice if you can provide a tutorial on how to write a buildscript for using these tools on a common bundle/content folder structure in AEM. Thanks!