[ http://jira.codehaus.org/browse/MNGECLIPSE-191?page=all ]
Eugene Kuleshov closed MNGECLIPSE-191.
--------------------------------------
Resolution: Won't Fix
As been discussed, the recommended approach would be to change mapping in
pom.xml, so both command line and ide will have the same project structure.
This creating proper project structure from pom.xml supposed to be
automatically taken care by Update Source Folders action, which should be fixed
before 0.0.10 release.
> support inplace webapp deployment
> ---------------------------------
>
> Key: MNGECLIPSE-191
> URL: http://jira.codehaus.org/browse/MNGECLIPSE-191
> Project: Maven 2.x Extension for Eclipse
> Issue Type: Improvement
> Reporter: Mike McMahon
> Priority: Minor
> Attachments: inplace.patch
>
>
> Currently, maven-built webapp projects (with or without m2eclipse) are
> difficult to debug efficiently
> using Eclipse. My definition of "efficient" debugging of a webapp (using
> Tomcat for example) is:
> - HTML and JSP pages immediately seen upon edit/save then browser refresh/F5
> - Java class changes are HotSwapped into the running JVM, stack is rewound
> - Java class changes are immediately placed into Tomcat WEB-INF/classes
> My recommended approach is that m2eclipse should make a .classpath which
> enables the Eclipse
> builder (org.eclipse.jdt.core.javabuilder) to fully assemble an "exploded
> war" deployment of
> the webapp. An example classpath is as follows:
> <classpath>
> <classpathentry output="src/main/webapp/WEB-INF/classes" kind="src"
> path="src/main/java"/>
> <classpathentry kind="src" path="src/test/java"/>
> <classpathentry output="src/main/webapp/WEB-INF/classes" kind="src"
> path="src/main/resources"/>
> <classpathentry kind="con"
> path="org.eclipse.jdt.launching.JRE_CONTAINER"/>
> <classpathentry kind="con"
> path="org.maven.ide.eclipse.MAVEN2_CLASSPATH_CONTAINER"/>
> <classpathentry kind="output" path="target/classes"/>
> </classpath>
> A more complex case (multi-module build having multiple source trees) would
> work by assembling
> ALL of the classes and resources into a single webapp location.
> This approach diverges from the current m2eclipse philosophy of having the
> Eclipse build "mirror"
> the maven build. I dont see much actual value in synchronizing these 2
> independent builds, especially
> when so much productivity is gained by using the Eclipse build for inplace
> webapp purposes.
> Patch attached
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
