Jean-Sebastien Delfino wrote: > Maven 2 seems to generate the correct Eclipse project structure! > > To get all the Eclipse .project and .classpath files generated > correctly, you just need to run mvn eclipse:eclipse from the > contrib/java/trunk directory. The Maven Eclipse plugin correctly > translates the Maven artifact dependencies to Eclipse project > dependencies, so incremental compile, reference searching and > refactoring should work ok in Eclipse. > > Jeremy did you try to run the Idea plugin from the top of the tree as > well? Initially I ran mvn eclipse:eclipse from the individual project > directories and the generated .classpath files were not right, pointing > to the Maven repos instead of the other generated projects, this looks > similar to what you're observing with the Idea plugin. Maybe if you run > Maven from the top it'll do the trick? >
That is where I ran it from. From what it generated it looked like it basically treated each project as a separate thing and generated an Idea module for it, then added all those modules to one project. Inter-module dependencies were not generated and the Maven project dependencies were added as libraries for each module. > I'll test the samples and if everything works well in the IDE with the > generated projects then I'll remove the Eclipse .classpath and .project > files from SVN, it's much cleaner and maintainable this way. > If it works for Eclipse then let's remove both and I will keep the Idea files somewhere separate. -- Jeremy
