Yes. It sort of works for me. The 0.0.4 plugin does *not* read the settings.xml file, which is pretty limiting, but I have used it successfully.
It works best, IMHO, if you "enable" the Maven2 nature, which puts a Maven2 container in your .classpath file instead of listing each jar separately. That way, when you edit your pom.xml the dependencies are automatically updated. But since it doesn't read your settings.xml, it will have trouble getting to a local repository if that repository requires authentication. -K -- Kathryn Huxtable Middleware Architect Core Middleware Information Technology, a division of Information Services The University of Kansas On 1/30/06 8:39 PM, "Maciej Mastalarczuk" <[EMAIL PROTECTED]> wrote: > Hi, > > > > Has anyone had any luck with using Maven 2 with Eclipse? It can be easily > integrated through external launch configuration, but Eclipse build paths > are pain. I know there is a plugin for Eclipse > (http://m2eclipse.codehaus.org), but the latest version (0.0.4) seems to be > completely broken as it does not want to download anything; just says > something about authentication being cancelled. The previous version (0.0.3) > is slightly better, but it has the older version of Maven embedder (2.0 beta > 4 SNAPSHOT) and seems to download wrong stuff. I am using maven 2.0.2. > > > > Has anybody got it working properly? I mean having a Maven 2 project with > all dependencies resolved in Eclipse. > > > > Thanks in advance > > > > Maciej Mastalarczuk > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
