Having run clean installs a few times I noticed a few things: True, some of the projects, including maven-plugins are seperated, requiring them to be run seperately.
Sometimes (depending on how cleanly seperated dependencies are) you have to run "mvn -fn install" a couple of times before it "takes", since a module may fail, causing the parent to fail as a whole, but working the second time because the individual modules did pass. This may not be an issue in production source, but something I've noticed can happen if you grab the latest and greatest. Note: I don't have Maven installed anywhere within 500 miles of where I am, but that command line parameter is supposed to be the "no fail" param... I believe it is "-fn". Eric On 12/9/05, Nitko2 <[EMAIL PROTECTED]> wrote: > > Hi. > > I checked out maven 2 v2.0 code, and ran mvn eclipse:eclipse in order to > create eclipse projects. > > .project and .classpath files were created except for maven-plugins > subdirectories. So I ran mvn > eclipse:eclipse in maven-plugins directory. > > After that I got error about missing dependencies. In particular some > plugins depend on some other > plugins with version 2.0-beta-4-SNAPSHOT. Those versions are obviosuly > removed from repository. > > I would like to execute maven inside eclipse using latest stable release > and that is v2.0. > > So my question is: how can I accomplish that? > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
