on to any party other than intended recipient. Sender does
not necessarily endorse content contained within this transmission.
> Date: Thu, 7 Aug 2008 05:10:09 -0700
> From: [EMAIL PROTECTED]
> To: users@maven.apache.org
> Subject: Re: tomcat webapp and eclipse
>
>
>
>
Istvan Devai wrote:
>
> I've tried this. I've configured Jetty as a WTP server and added a Jetty
> context file to point to /target/myapp-1.0-SNAPSHOT. It worked, however,
> if I edited a random .html file in Eclipse, these changes were not
> copied to /target/myapp-1.0-SNAPSHOT, only after I
Both Q4E and m2eclipse plugins (for Maven support in Eclipse) do resource
filtering. I suppose you could point to the webapp target directory for
src/main/webapp and then use that as a context, but in general I think
filtering all of your webapp resource files is a bad idea (because I imagine
it'd
Hi Johan,
I've tried this. I've configured Jetty as a WTP server and added a Jetty
context file to point to /target/myapp-1.0-SNAPSHOT. It worked, however,
if I edited a random .html file in Eclipse, these changes were not
copied to /target/myapp-1.0-SNAPSHOT, only after I ran mvn package.
Ho
Hi Kalle,
Thank you for your reply.
Yesterday I spent a few hours tinkering with various setups and realized
that mvn jetty:run basically works in the way you described below
(classes from /target/classes, webapp resources from /src/main/webapp).
This works nicely, and - as you kindly describ
Wtp and the maven plugin for eclipse works for me.
Prereqs: wtp1.5, 2.x or 3.x
1. Define classpath variable M2_REPO in eclipse, pointing to your
maven repo.
2. Run mvn command...
mvn -U -Dwtpversion=1.5 eclipse:clean eclipse:eclipse
3. Import the generated project into eclipse
Ready to go!
If you use Sysdeo's Eclipse Tomcat Launcher plugin (
http://www.eclipsetotale.com/tomcatPlugin.html) and its devloader, you can
point to src/main/webapp for context, pick up the class files from
target/classes and the libraries from your local m2 repo directories. It's
both faster and more reliable
