Re: [m2eclipse] Eclipse WebTools and Maven2 Publishing Failed

2006-02-04 Thread Fabrizio Giustina
Publishing failed Resource /M2_REPO/commons-logging/commons-logging/1.0/commons- logging-1.0.jar does not exist. That's a WTP bug, in any version from WTP 1.0 till recent builds: https://bugs.eclipse.org/bugs/show_bug.cgi?id=116783 WTP 1.0 simply ignores external dependencies, later builds

Re: [m2eclipse] Eclipse WebTools and Maven2 Publishing Failed

2006-02-04 Thread John Fallows
Hi Fabrizio, On 2/4/06, Fabrizio Giustina [EMAIL PROTECTED] wrote: Publishing failed Resource /M2_REPO/commons-logging/commons-logging/1.0/commons- logging-1.0.jar does not exist. That's a WTP bug, in any version from WTP 1.0 till recent builds:

RE: [m2eclipse] Eclipse WebTools and Maven2 Publishing Failed

2006-02-03 Thread Domsch, Christian
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

Re: [m2eclipse] Eclipse WebTools and Maven2 Publishing Failed

2006-02-03 Thread John Fallows
On 2/3/06, Domsch, Christian [EMAIL PROTECTED] wrote: 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

Re: [m2eclipse] Eclipse WebTools and Maven2 Publishing Failed

2006-02-03 Thread Lee Meador
There was a bug that showed up when you had spaces in the repository location you told the maven2 eclipse plugin. You should try using the short name for documents and settings that you can get doing a dir /x in a dos box. The short name, on my machine, is DOCUME~1 for that folder. It lets you get

Re: [m2eclipse] Eclipse WebTools and Maven2 Publishing Failed

2006-02-03 Thread John Fallows
Thanks Lee, I'm trying this from home, so no proxy at the moment, although settings.xmlintegration will become more important later. :-) I tried your suggestion, but it did not seem to help. Just in case Eclipse or the Maven2 Eclipse plugin was being too smart and converting the short-name path