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?
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.
--
Jean-Sebastien
Jeremy Boynes wrote:
Jeremy Boynes wrote:
I'd suggest getting to m2 then try the generation again. If it works
then we are set and can just remove them, if not then let's figure out
how we can remove them from the trunk but still provide them for new users.
I tried the idea generation and it seemed to generate a bunch of
individual projects. Although the modules were all there, they were all
isolated from each other which makes me think that things like global
refectoring would not work properly.
--
Jeremy
