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 to a canoncial path with spaces, I even relocated the
<localRepository> to C:\m2repos, eliminating all spaces, but still no joy.
;-(
The .settings/.component file does have all the relevant entries for each
deployed JAR in the webapp, for example:
<dependent-module deploy-path="/WEB-INF/lib"
handle="module:/classpath/var/M2_REPO/commons-logging/commons-logging/1.0/commons-
logging-1.0.jar">
<dependency-type>uses</dependency-type>
</dependent-module>
...but I still get the following error message:
Publishing failed
Resource /M2_REPO/commons-logging/commons-logging/1.0/commons-
logging-1.0.jar does not exist.
Is it possible that M2_REPO is really not defined during WTP deployment?
Or could this be a more general problem with any classpath variable?
Any pointers would be greatly appreciated. :-)
Kind Regards,
John Fallows.
On 2/3/06, Lee Meador <[EMAIL PROTECTED]> wrote:
>
> 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 rid of the spaces.
>
> The maven2 eclipse plugin 0.0.4 does not work with the proxy that you set
> in
> settings.xml. This leads to some "issues" if you need a proxy to let you
> through to the remote repository.
>
> Maybe that could help.
>
> On 2/3/06, John Fallows <[EMAIL PROTECTED]> wrote:
> >
> > 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 claim this has been solved since WTP 1.0M2
> > > or something like that.
> > > (https://bugs.eclipse.org/bugs/show_bug.cgi?id=87474)
> >
> >
> > Thanks for the pointer, Christian. This does indeed seem like the same
> > bug,
> > however it looks to be broken in my environment for Eclipse 3.2M4 and
> WTP
> > 1.5M4 and your environment for Eclipse 3.1.2 and WTP 1.0.
> >
> > Anyone else having similar difficulties, or better yet, a solution?
> >
> > Kind Regards,
> > John Fallows.
> >
> > > -----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]
> > >
> > >
> >
> >
> > --
> > http://apress.com/book/bookDisplay.html?bID=10044
> > Author: Pro JSF and Ajax: Building Rich Internet Components, Apress
> >
> >
>
>
> --
> -- Lee Meador
> Sent from gmail. My real email address is [EMAIL PROTECTED]
>
>
--
http://apress.com/book/bookDisplay.html?bID=10044
Author: Pro JSF and Ajax: Building Rich Internet Components, Apress
