WTP support is a major issue for me as well. Here are two different alternatives I've found work:
a) Instead of the plugin, use: mvn eclipse:eclipse -Dwtpversion=R7 (for Eclipse 3.2 and 3.3, with some difficulty with Eclipse 3.3.1.1). This generates a .project, .classpath, and .wtpmodule file. In Eclipse 3.3, this .wtpmodule needs to be upgraded to the new .settings/* format, so right click on the ensuing warning and select "quick fix". In Eclipse 3.3.1.1 the eclipse file formats changed again, so it takes a bit more effort to get this method to work, but it can be done. b) Use the plugin to do development, but don't use the WTP project natures/builders. Instead do manual command line builds and deploy the war to tomcat. Then attach Eclipse to the remote tomcat/jboss/etc JVM to use debugging. This works wonderfully. Doug -----Original Message----- From: Adam Hardy [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 29, 2008 6:40 AM To: [email protected] Subject: Re: [m2eclipse-user] how can I work-around WTP dependency deployment problems? I guess that we still use maven but just not m2eclipse. I think how you judge the trade-off between functioning jar dependency management versus functioning project dependencies depends entirely on what stage of the development lifecycle you are. At the moment I am writing JSPs and developing a taglibrary which is in one of the project dependencies - so I've turned off m2eclipse dependency management. I'll probably turn it back on later (and close the projects on which my main project depends). I would also love to help but haven't heard much discussion around here lately on development. I think we see it happening in concentrated bursts, but I'm not sure if it's like that. Henri Gomez on 29/01/08 09:00, wrote: > Same problem here and I'll be happy to see it solved since it prevent > me to move some webapp projects to maven (which is sad). > > I should remove the WTP natures to have maven resolve dependencies : > > <nature>org.eclipse.wst.common.project.facet.core.nature</nature> > <nature>org.eclipse.wst.common.modulecore.ModuleCoreNature</nature> > > I got Latest Eclipse and WTP > > How can we help ? > > 2008/1/25, Adam Hardy <[EMAIL PROTECTED]>: >> I'm trying to work-around the "Workspace dependencies not added to >> classpath container for WST dynamic web projects" >> http://jira.codehaus.org/browse/MNGECLIPSE-438 >> >> So far, I have changed my pom so that the packaging is now JAR >> instead of WAR and my web project compiles now. >> >> However, the second part of the bug still affects me: WTP fails to >> put the project dependency into the tomcat classpath. >> >> Is there a work-around for this? (Apart from closing the project >> dependency I mean!) >> >> Can I manually add entries to my .classpath or my >> .settings/org.eclipse.wst.common.component to fix it? --------------------------------------------------------------------- To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email --------------------------------------------------------------------- To unsubscribe from this list please visit: http://xircles.codehaus.org/manage_email
