Details
-
Type:
New Feature
-
Status:
Closed
-
Priority:
Major
-
Resolution: Not A Bug
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: Maven
-
Labels:None
-
Number of attachments :
Description
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 we have to work with WAR overlays so that the central maven project is created by an overlay over another artifact. 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 runs with this path to lookup static resources. 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 in overlay projects as a redeploy or restart of the app is not necessary actually.
Activity
| Field | Original Value | New Value |
|---|---|---|
| Assignee | Jan Bartel [ janb ] |
| Status | Open [ 1 ] | Closed [ 6 ] |
| Resolution | Not A Bug [ 6 ] |