does anybody else find the new way to pass VM parameters (especially -D ones) to
a Tomcat process a little too awkward? The possibility to pass environment variables
is a little too generic IMO. There are a few points I have issues with:
- To pass VM arguments I have to know how the startup scripts of Tomcat work, i.e.
that they use a variable named "JAVA_OPTS". In the "Run" tab it is possible to create
this variable. However, editing a variable with long values is a pain in this small
table cell. This needs at least an additional edit dialog like it was in 4.0.
- In the "Debug" tab, the JAVA_OPTS are not editable at all. No way to define any additional
VM option as far as I can see.
- The environment variables are not shared between the Run and Debug configuration.
That's pretty bad because it will make the whole thing behave differently when those
vales are not totally in sync. Those things are hard to catch.
My suggestion: Since it's not a totally generic Run configuration anyway (it's still called
"Tomcat"), the usage should be much easier. The environment variables table should actually
be a table to edit VM parameters in a convenient way. Is there any use for generic env. vars
Actually I'm not too fond of the way to start the server via its supplied scripts. I think
the way to start it in 4.0, with the possibility to include the module classpath, was more
straight forward to use. It was much easier before to run a webapp that just consisted of a
web.xml that declared some servlet that's somewhere in my project: I didn't have to care
about what files to deploy where, just a single click and IDEA could run the webapp. Not to
mention the time it currently takes to build a 10Mb .war file or to copy the stuff to the
PS: In case I can't make friends with the new method, would it be theoretically possible
to convert the 4.0 Tomcat plugin to work with 4.1?