i guess that reading this table:
http://docs.codehaus.org/display/JETTY/What+files+are+scanned+by+the+Jetty+Maven+Plugin
gives me some hint about what's going on. the scanTargets is only used by
the run goal....
On 10/31/06, Valerio Schiavoni <[EMAIL PROTECTED]> wrote:
hello everyone,
i'm using the jetty plugin to test and deploy my webapp. because i'm using
filtering (on both web.xml content and on other properties) , i launch
everything with:
mvn jetty:run-exploded
then, if i try to edit a jsp file in the src/main/webapp/WEB-INF/jsp
and i hit 'refresh' on the browser, i don't see the changes. i guess it
measn that the page has not been hot-redeployed. everything was working fine
with mvn jetty:run (which makes sense because it deploy the webapp in-place,
afaik).
this is how i configured the plugin:
<plugin>
<groupId>org.mortbay.jetty</groupId>
<artifactId>maven-jetty-plugin</artifactId>
<configuration>
<scanIntervalSeconds>5</scanIntervalSeconds>
<webDefaultXml>${jetty.webdefaultxml}</webDefaultXml>
<!-- this scan targets are added to the default ones -->
<scanTargets>
<scanTarget>src/main/webapp</scanTarget>
</scanTargets>
</configuration>
</plugin>
the version of jetty being uses is:
[INFO] Starting jetty 6.1.0pre0 ...
thanks,
valerio
--
http://valerioschiavoni.blogspot.com
http://jroller.com/page/vschiavoni
--
http://valerioschiavoni.blogspot.com
http://jroller.com/page/vschiavoni
