Pom.xml settings:
Critical row, scan period (10 seconds), change restart <scanIntervalSeconds>10</scanIntervalSeconds> local Setup code:<build><!-- Jetty plugin, set context path and spring profile--><plugin><groupid>org.mortbay.jetty</groupid>< artifactid>jetty-maven-plugin</artifactid><version>${jetty.version}</version>< Configuration> <scanIntervalSeconds>10</scanIntervalSeconds> <systemProperties>< systemproperty><name>spring.profiles.active</name><value>development</value></ systemproperty></systemproperties><usetestclasspath>true</usetestclasspath>< webappconfig><contextpath>/${project.artifactid}</contextpath></webappconfig></ Configuration></plugin></build>
set the Run as--->run configuragtions---the >JRE label Property vm arguments:
-server-xms512m-xmx1024m-xx:permsize=512m-xx:maxpermsize=512m-xx:+cmsclassunloadingenabled-xx:+printgcdetails- Xloggc:%m2_home%/gc.log-xx:+heapdumponoutofmemoryerror-xx:heapdumppath=%m2_home%/java_pid.hprof
Setting maven_opts does not work, the above settings can work.
Maven jetty development in eclipse effective settings for hot deployment