Archetype should support building and deploying bundle only


In the current setup of the Maven Archetype it does not support the build and deploy of the bundle (core module) as a separate step. The breakdown in small modules with separate scripts works well overall, but the lack of a separate script for the bundles means we have to do a complete build and deploy for our new bundles to be installed. This slows down the development.

Functionality like autoInstallBundle could solve this.


Stefan Seifert
August 5, 2019, 2:02 PM

deployment for individual bundles can be done by using


which is equivalent to

i think this information is missing from the generated README files!

Jurgen Brouwer
August 5, 2019, 2:08 PM

Great, that's pretty much what I was looking for! If this can be added to the README that would be excellent.

One small thing: this deploys to the author. How would I run this for the publish?

Stefan Seifert
August 5, 2019, 2:09 PM

for example with:

there is currently nor predefined profile for switching the port to publish (but maybe we should add one)

Jurgen Brouwer
August 5, 2019, 2:25 PM

Great! That works for me, we can easily use these commands during development.

Yes, adding a predefined profile would probably make sense. I was initially looking for one to get this working.


By the way: thanks for the super quick response :)

Stefan Seifert
August 19, 2019, 8:47 AM

documentation about "cq:install" goal updated in the README of the AEM archetype 2.4.0.

additionally i've refactored the way the publish URL is maintained - it's now only defined in the parent pom, and reused from all scripts. switch to publish is possible with maven profile -Ppublish.




Stefan Seifert


Jurgen Brouwer




Fix versions

Affects versions