jetty:run seems to not notice changes to templates inside WEB-INF in your web app if you are using a war overlay

when using web apps using war overlays (e.g. one of the samples in Scalate which reuses the scalate console using an overlay), changing templates don't seem to get recognised in jetty:run. To re-evaluate a template you have to stop & restart "mvn jetty:run"!

However if we zap the redundant copy of the source templates from src/main/webapp which get copied into target/tmp/webinf/WEB-INF/ then it all works fine.

The question is, since the source of target/tmp/webinf/WEB-INF is all available in src/main/webapp/WEB-INF - why does the maven plugin make a redundant copy when using overlays - that then breaks reloading.

Maybe it needs to only copy stuff to target/tmp/webinf/WEB-INF if there is not a file of the same name in src/main/webapp/WEB-INF? i.e. delete the stuff from the overlay which exists in src/main/webapp/WEB-INF?