Details
-
Type:
New Feature
-
Status:
Open
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: 8.0.4
-
Fix Version/s: None
-
Component/s: Maven
-
Labels:None
-
Number of attachments :
Description
[Plagiarized from JETTY-1095, referring to filtered resources instead of overlays.]
The run goal of the maven-jetty-plugin automatically picks up changes in src/main/webapp automatically so that changes on JSPs, CSS and other stuff are available instantly after editing the files. Now suppose a scenario where these static assets are modified by resource filtering. Running this scenario can be achieved with jetty:run-exploded easily. In this case the Jetty plugin assembles the app to deploy in target/$
{finalName}by default. Thus Jetty is able to serve static assets that have had resource filtering applied. The problem is that changes to the static resources now don't get picked up as they only affect files in src/main/webapp.
So what I am looking for is a simple hot replacement of static resources as a redeploy or restart of the app is not necessary actually.