Le mercredi 30 mai 2007 à 07:28 +0000, Martin Grotzke a écrit : > For me changed classes are not picked up automatically, when running > mvn jetty6:run... > If it's working for you, what's your setup, or did you do anything > special to support class reloading? Is it connected with a context > reload of your servlet container (what AFAICS should not be necessary)?
Well... I encounter some strange behaviour with mvn jetty:run and class reloading. It works perfectly at my work, and jetty fire some exception about unimplemented class reloading functionality in fresh install of eclipse 3.2 at home. So, the way that seems to just work is to use jetty 5 + jetty launcher plugin, as show in the tutorial ( http://tapestry.apache.org/tapestry5/t5-tutorial.pdf ), and let mvn apart for that task. If some one has a procedure to have mvn jetty:run + jetty 6 (0 or 1) + class/template reloading work, or just can explain what factors make it work or not, I will be glad to know them. Hope it will help, Francois --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
