In the current setup of the WCM.io 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.
deployment for individual bundles can be done by using
which is equivalent to
i think this information is missing from the generated README files!
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?
for example with:
there is currently nor predefined profile for switching the port to publish (but maybe we should add one)
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 :)
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.