This seems related to MNG-2277, which was fixed in 2.0.8. Are you seeing this on 2.0.8 or earlier?
-----Original Message----- From: Martin Höller [mailto:[EMAIL PROTECTED] Sent: Thursday, March 06, 2008 5:41 AM To: Maven Users List Subject: Re: Try to run install before eclipse:eclipse On Thursday 06 March 2008 [EMAIL PROTECTED] wrote: > Making install run before eclipse:eclipse is a bad idea in some cases. We would need it only in multi-module projects if some artifacts cannot be found in the repository. > In particular, when a project doesn't compile it is currently possible > to still run eclipse:eclipse. Making install a pre-requisite would > block that, which would be really anoying. Good point! A new developer should not only be able to join the team if the project compiles right now. > I think what the original poster is saying is that > eclipse:eclipse > is correctly generating all of the eclipse projects, but that eclipse > then displays build errors because the jars that the newly created > eclipse projects point to don't yet exist. No, mvn eclipse:eclipse fails in a multi-module project, if the artifacts are not in a (local or remote) repository, even if they could have been built. See also this thread for some more details: http://www.nabble.com/maven-eclipse-plugin-with-multi-module-projects-to15222495s177.html hth, - martin -- Martin Höller | [EMAIL PROTECTED] *x Software + Systeme | http://www.xss.co.at/ Karmarschgasse 51/2/20 | Tel: +43-1-6060114-30 A-1100 Vienna, Austria | Fax: +43-1-6060114-71 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
