Not sure, we always perform dependency resolution before generating project files. Besides if the project doesn't compile in the version control this often means you have much bigger problem. :)
Anyway try mvn process-resources, this seems to run just before compilation begins and should resolve dependencies. For more details see the manual: http://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html#Lifecycle_Reference On Feb 1, 2008 9:22 AM, Martin Höller <[EMAIL PROTECTED]> wrote: > Hi all! > > I have an issue with the m-eclipse-p and a multi-module prject. The > scenario > is as follows: > > Parent Project P > | > +-- Project A > | > `- Project B > > B has a dependency on A (B requires A). > > A user with an empty local repository cannot checkout the whole project > and > run 'mvn eclipse:eclipse' due to unsatisfied dependencies. The build will > fail in Project B because Project A is missing from the repository. > > A 'mvn install' has to be executed before (at least for Project A). But > what > if the project is in a state where it doesn't compile? It's not possible > in > this case for a new user to start developing with eclipse. > > Am I missing something here? > Is there an oportunity to tell maven to skip dependency checking? > > regards, > - 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 >
