Hello, we do have the same problem (its not a M4 specific problem, it also shows up on eclipse 3.1.2 with WTP 1.0). I would really like to have a solution to that.
Btw, I scanned the eclipse wtp bug list and found something on there. But they claim this has been solved since WTP 1.0M2 or something like that. (https://bugs.eclipse.org/bugs/show_bug.cgi?id=87474) Greetings Christian. > -----Original Message----- > From: John Fallows [mailto:[EMAIL PROTECTED] > Sent: Freitag, 3. Februar 2006 07:05 > To: Maven Users List > Subject: [m2eclipse] Eclipse WebTools and Maven2 "Publishing Failed" > > > I'm trying to use Eclipse 3.2M4, Eclipse WebTools 1.5M4, > Maven2 Eclipse > Plugin 0.0.4 and Tomcat 4.1. > > I have a WebTools Dynamic Web Project that uses Maven2 to > resolve library > dependencies. When trying to "Debug As -> Debug on Server", > the following > error occurs: > > Publishing failed > Resource /M2_REPO/commons-logging/commons-logging/1.0/commons- > logging-1.0.jar does not exist. > > It seems as though the "M2_REPO" variable is not being > resolved correctly > when the WAR is being constructed for deployment to Tomcat. > > Presumably this should resolve to > C:\Documents and > Settings\john.fallows\.m2\repository/commons-logging/commons-l > ogging/1.0/commons- > logging-1.0.jar > > which does exist on the local filesystem. > > Note that I have already set the Maven2 Preferences to use > "C:\Documents and > Settings\john.fallows\.m2\repository" as the Local Repository > Folder value, > enabling compilation to succeed. > > Btw, this type of IDE integration is exactly the right > direction for Maven2 > to be taking. Combined with automatic generation of all the > various flavors > of IDE project files, we are getting very close to having a > single source of > truth for both IDE development activities and continuous integration > builds. Great work! > > Kind Regards, > John Fallows. > -- > http://apress.com/book/bookDisplay.html?bID=10044 > Author: Pro JSF and Ajax: Building Rich Internet Components, Apress > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
