Dear all, As I was upgrading the maven jetty plugin in a struts archetype, I noticed a difference in behaviour between versions 6 and 8 of the plugin. While this might be due to a change in jetty's configuration, I thought we should check this and probably update the archetypes accordingly.
Essentially, with version 6, changes in a JSP are automatically seen (without redeployment) by refreshing the broswer. In version 8, you need to redeploy the jetty container to see the changes. Steps to replicate (in either an IDE or command line): 1) Create a maven project with the struts2-blank-archetype 2) Edit the pom.xml file so the plugin section matches [1] 3) Run the jetty:run maven goal. 4) Open the browser and see the welcome page 5) Edit the file /src/main/webapp/WEB-INF/content/hello.jsp 6) Refresh the browser. You should see the changes immediately 7) Repeat 1-6, but update the plugin section in 2 to the contents listed below [2] Expected: Same result as before Actual: You no longer see the jsp changes upon refreshing the bowser. You need to restart jetty! [1] - Version 6 of the plugin. The scantarget element was removed because we don't want a complete server redeployment when we just change a JSP. <plugin> <groupId>org.mortbay.jetty</groupId> <artifactId>maven-jetty-plugin</artifactId> <version>6.1.21</version> <configuration> <scanIntervalSeconds>10</scanIntervalSeconds> </configuration> </plugin> [2] - Version 8 of the plugin. Exact same configuration (except for the artifact's name and version) <plugin> <groupId>org.mortbay.jetty</groupId> <artifactId>jetty-maven-plugin</artifactId> <version>8.1.7.v20120910</version> <configuration> <scanIntervalSeconds>10</scanIntervalSeconds> </configuration> </plugin> Does anyone know what configuration change is needed so you get the same behaviour as before? Miguel Almeida