So, provided that adding hot redeployment features (jetty:run or some Jrebel like solutions) is on the roadmap, for now I think that to make the best out of what we have a couple of options are possible:
Using 2 AMPs archetypes:
1. Use the AMP archetype to create a repo AMP
2. Use the AMP archetype to create a share AMP (set alfresco.client.war=share)
3. Configure the share AMP to run on port 8081
4. Run each of them in separate shells with mvn clean integration-test -Pamp-to-war
5. When changing Share AMP, only restart the share AMP
6. When changing Alfresco AMP, well restart the repo even though that can be slow
Speeding up the all-in-one:
1. Run 'mvn clean install' once from the root (all apps get built)
2. Go into the runner folder
3. 'mvn integration-test -Prun' from that folder will only run the apps, not build them
4. While developing, rebuild only the WAR you need and repeat step 3
Said that, I noticed the most time is spent in WAR overlays, which are especially slow on the my Mac because of lots of chmod / chown operations (probably preserving WAR contained files permissions while unpacking). I'll look to speed up this, hopefully there is some archiver/war-plugin options I can use.
Sorry again for the late answer, hope this helps still.
Gab
--
Gabriele Columbro
Principal Architect, Consulting Services
Alfresco Softwaretwitter:
@mindthegabz
blog:
http://mindthegab.commobile:
+31627565013