Thanks for the tips. This is working much better for me now and I'm now much
more productive.
--
Jason
Martijn Dashorst wrote:
Not recommended per se, but it works for me. However, it will not
reload structural changes, you'll need to restart jetty when you add a
property, method, or
I think most developers have given up on using the eclipse jetty
plugin, and use an embedded container instead. That one doesn't
hot-deploy (or at least not in our configurations). To get changes in
classes we run the application in the eclipse debugger. See [1] for a
starter class.
If you want
I think most developers have given up on using the eclipse jetty
plugin, and use an embedded container instead.
Jason uses the Maven Eclipse plugin, which is a completely different
bird, and which actually is used by quite a few developers from what I
hear.
Eelco
Not recommended per se, but it works for me. However, it will not
reload structural changes, you'll need to restart jetty when you add a
property, method, or change the signature of a method, etc.
The debugger can only modify the contents of methods, not add them
(unfortunately). The reloading
Thanks Eelco. However, I am using the Maven Jetty plugin
(http://www.mortbay.org/maven-plugin/index.html) for jetty usage under
Maven. Perhaps that is what you meant. I am also using the Maven2 eclipse
plugin (http://m2eclipse.codehaus.org/) for dependency management within
eclipse, but that
On 10/5/07, Martijn Dashorst [EMAIL PROTECTED] wrote:
Not recommended per se, but it works for me. However, it will not
reload structural changes, you'll need to restart jetty when you add a
property, method, or change the signature of a method, etc.
The debugger can only modify the contents
I have been successfully developing a Wicket application with Eclipse, Maven,
and the Maven Jetty plugin with hot redeploy enabled. However, I don't want
Jetty to do a hot redeploy of the application when I make a change to my
HTML files. I assume that Wicket will pick up these changes
