jetty's hot deploy feature does not work for me

[GoogleCodeExporter]

I am running the plugin in a maven-based project which uses wicket. The 
configuration for the jetty maven plugin looks like this:

<groupId>org.mortbay.jetty</groupId>
    <artifactId>maven-jetty-plugin</artifactId>
    <version>6.1.4</version>
    <configuration>
        <scanTargets>
            <scanTarget>src/main/resources/</scanTarget>
            <scanTarget>src/main/webapp/</scanTarget>
        </scanTargets>
    <scanIntervalSeconds>10</scanIntervalSeconds>
</configuration>

With the above configuration the plugin restarts jetty nicely whenever I 
change any page classes.

With the run-jetty-run I have so far been completely unable to activate my 
changes unless I manually restart the plugin.

Original issue reported on code.google.com by mdie...@gmail.com on 3 Sep 2008 at 9:47

[GoogleCodeExporter]

A nice way to reload classes (without reloading the whole application) is 
provided by
javarebel (http://www.zeroturnaround.com/javarebel/). Follow the javarebel
installation instructions and add s.th. like "-noverify 
-javaagent:lib/javarebel.jar
-Drebel.dirs=target/classes" to the vm arguments of the  run configuration of
run-jetty-run.

Cheers, Martin :)

Original comment by martin.grotzke on 1 Mar 2009 at 10:34

[GoogleCodeExporter]

Issue 7 (locking of static files) may be impacting you.  Nonetheless, version 
1.1 of 
the plugin may address some of the problems you're encountering (it does for 
me: when 
I edit a Java source file in a project that my web app project depends on, the 
JVM 
picks up the changes right away).  Of course, if the JVM can't handle hot 
replace of 
the change, then you're out of luck.

Please update this bug to let me know if the problem is resolved by 1.1.

Original comment by James.Sy...@gmail.com on 4 May 2009 at 1:04

• Changed state: More-Info

[GoogleCodeExporter]

Original comment by tonylovejava on 1 Jul 2011 at 8:34

• Changed state: Invalid