Sammy wrote:
This is probably a beginner's question, so excuse me in advance!
I would like to know if it is preferable, while using m2eclipse, to
define a Server Runtime (like Apache Tomcat 6.0 for instance) and
debug against it using Run As->Run on Server within the eclipse
project's context menu OR use the m2eclipse plugin to define a build
such as jetty:run.
The "Maven integration for WTP" feature is designed to work with WTP,
and it provides support for "Run as... / Run on server". This feature
been tested with Tomcat, Jetty and JBoss servers.
If you don't want to use WTP, then jetty:run should work too, though I
am not sure about developer workflow, e.g. how hot deployment of the
changed classes is supported in such configuration. It would be great if
someone investigated this and document it on the wiki.
BTW, there is some old documentation about starting various
application servers from Maven at
http://docs.codehaus.org/display/M2ECLIPSE/Using+Maven+with+application+servers
While we're on it, I wonder if there's a maven plugin that actually
configures server runtime's within eclipse according to which server
one is using within the POM file.
The m2eclipse does not using Maven plugins for configuring things in
Eclipse. Instead it is using extensible project configuration framework
[1] that allows to read configuration from pom.xml and configure things
in Eclipse accordingly.
It would be a neat enhancement to add support for configuring server
runtimes using configuration from pom.xml. Would you mind to open an
enhancement request for that in the project jira at
http://jira.codehaus.org/browse/MNGECLIPSE ?
Thanks
Eugene
[1]
http://docs.codehaus.org/display/M2ECLIPSE/Extensible+project+configuration+framework
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
