Krystian Panek
Krystian Panek
usage: `sh gradlew :app:aem:all:zip -PmvnBuild.skipTests`
try both options mentioned in issue: bndtools/bnd#4779
``` * What went wrong: Execution failed for task ':env:aem:instanceProvision'. > Cannot perform provision step 'enableCrxDe' on LocalInstance(name='dev-author', httpUrl='http://localhost:4502')! Cause: Cannot save repository node '/var/gap/provision/step/enableCrxDe' on LocalInstance(name='dev-author', httpUrl='http://localhost:4502'). Cause: Failed...
bump plugins written by scaffolder too
https://github.com/wttech/gradle-aem-plugin/blob/master/src/main/kotlin/com/cognifide/gradle/aem/common/instance/LocalInstance.kt#L308 the side effect possible is that when calling `instanceUp` task is implemented as starting systemd service, then when instance is already up then there is no effective trigger that...
instead ``` -PforkProp.localInstanceQuickstartJarUri=dir/instance/cq-quickstart-6.5.0.jar -PforkProp.localInstanceQuickstartLicenseUri=dir/instance/license.properties ``` it would be nice to have only ``` -PforkProp.localInstanceQuickstartDirUri=dir/instance ``` this will cause that by simply updating jar file, nothing else need to be configured....
I implemented protection wrapper code around it to have at least error reporting but still this situation should not happen. The only idea I have to fix it is to...
describe various scenarios - project needs only local AEM instances - project needs instances and AEM dispatcher - project builds app using Maven and wants to integrate it with local...
pre-configure: ``` tasks { register("integrationTest") { javaLauncher.set(aem.localInstanceManager.javaLauncher) } } ``` when ``` plugins { id("com.cognifide.aem.common") } ```
to report that build.maven.dot file should be regenerated e.g by calculating checksum of modules structure after generating build.maven.dot; if module changes then the new file will need to be generated...