Releases · wttech/gradle-aem-plugin

default path for local AEM instances instancesPath= "${System.getProperty("user.home")}/.aem/${project.rootProject.name}"
aemAwait now displays actual instance states while waiting for package installation
aemSatisfy and aemDeploy now respects new config parameter deploySnapshots which allows to force package reinstallation regardless same version currently installed on instance(s).

Assets 3

08 Sep 06:40

pun-ky

2.0.1

e85eade

Release 2.0.1

Implemented #57 , #55

Upgrade notes:

if project using plugin has using custom properties.xml with variables like ${project.group} etc, only syntax update is needed, from ${var} to {{var}} . This fixes just prevents against potential collisions with Felix variables in case of aemCreate task.

Assets 3

29 Aug 10:03

pun-ky

2.0.0

ce262d6

Release 2.0.0

Finally, we got stable 2.0.0 release with fully automated local AEM instances setup.
Also now

Implemented:

#52 | Plugin is covered by integration tests using Gradle TestKit.
#44 | Fully automated local AEM instances setup (aemSetup) with remote packages collecting and installation with stability checks (by default AEM Author and AEM Publish with debug ports opened, with dependent packages and application installed).
#49 | Merging filter roots improved (all-in-one packages generation)
includeProject, includeContent, includeBundles improved / cross project lifecycle dependencies
project.groupId, project.artifactId properties are now expandable as fallback for projects being migrated from Maven
config.fileProperties now can be used to specify non-existing properties being evaluated in XML files, for instance: project.build.finalName (other Maven legacy properties).
new task aemCollect which collects all CRX packages related with project and packs them into one ZIP to be able to easily transfer deliverables to client environments.

Upgrade notes:

apply plugin: 'com.cognifide.aem' change to apply plugin: 'com.cognifide.aem.package'
at the root of your aem project (or module) add apply plugin: 'com.cognifide.aem.instance' under apply plugin: 'com.cognifide.aem.package' to get instance related tasks like aemSetup, aemUp, aemSatisfy etc.
instance definition lines now are respecting type of instance (local or remote, author or publish) to be able to setup local instances by that configuration:

aem {
   config {
      instance("http://localhost:4502", "admin", "admin", "local-author")
   }
}

change to

aem {
   config {
      localInstance("http://localhost:4502" /* , "admin", "admin", "author", 14502 */)
   }
}

aem {
   config {
      remoteInstance("192.168.100.100:4502" /*, "admin", "admin", "publish", "integration" */)
   }
}

remember to wrap section above into section with new common id (for configuration shared between package and instance plugins)

    plugins.withId 'com.cognifide.aem.base', {

        aem {
            config {
                localInstance "http://localhost:4502"
                localInstance "http://localhost:4503"
            }
        }

    }

Assets 3