On Jan 9, 2008, at 4:39 AM, nicolas de loof wrote:
+1
Interesting way to use tomcat from eclipse as an alternative to
jetty:run, without requirement for packaging. I myslef used to run
war:inplace for similar purpose, but using devloader with this
plugin is even simplier.
It's a tool I stumbled upon a few years ago, and I've never been
convinced that it is the right way to develop web applications with
Eclipse. The main reason I use this tool is because every once in a
while, I have the need to set a breakpoint in something that runs in
plain-old Tomcat. I'm sure I could get the same thing with the web
development tools Eclipse ships with, but every time I try to use the
Eclipse Web Tools platform I always end up with an IDE that starts
consuming huge amounts of memory and tries to get me to change the way
I'm developing web applications.
I've always felt that the Sysdeo eclipse plugin was a little strange: http://www.eclipsetotale.com/tomcatPlugin.html
. I don't know how many people really use it, the plugin download
site briefly disappeared in 2006, and the tool isn't open source.
Other than those negatives, as long as there is a Maven plugin
generating .tomcatplugin, it tends to do it's job if you are careful
about keeping the contexts updated.
I'll promote this plugin in my coprporate maven toolbox, and
naturally contribute !
Great. Right now, I know a few people who use it. I've got 3 +1
votes, and the vote thread generated some bug fixes for session scoped
dependencies. I'll probably cut a release this upcoming weekend, and
then work on a 1.1 release that updates the dependency resolution
logic. After that, this might be one of those plugins that could be
considered "done".
Nico.
2008/1/6, Tim O'Brien <[EMAIL PROTECTED] >:
This plugin has been in the sandbox for a year. The site is here:
http://mojo.codehaus.org/sysdeo-tomcat-maven-plugin/
It was developed for people who happen to use the Sysdeo Tomcat
Eclipse Plugin. If you use that plugin and build your war packaged
projects with eclipse, you'll testify to the struggle you have
constantly making sure that provided scope dependencies are excluded
from the Sysdeo Tomcat Eclipse Plugin's classpath. You'll also be
familiar with the annoyance of having to cut and paste any content in
context.xml into the plugin's configuration. This plugin takes care
of that busy work and piggybacks on the Eclipse plugin to generate
the .tomcatplugin file automatically.
I've been using it without problems for a year, if anyone wants help
testing it let me know.
Tim
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
