For all the pain, Maven does one thing well - it externalizes
dependencies, so yes the plugin can figure out the jars (and you can
import an arbitrary combination of the new Mavenized projects in
Eclipse, so the requirements are actually less strict than they used
to be before).
But the plugin itself is rather raw - you'll have to run "mvn
eclipse:eclipse" from command line first, then import, then manually
edit .classpath to fix the incorrect pieces of the path generated by
"mvn eclipse:eclipse". And nothing would set the right JDK compliance
level in the process, so that's another step for you to do. In other
words, having a right .classpath in the beginning saves time.
And then we also have a .settings directory with all the class and
formatting templates. Also can be moved to "contrib/eclipse" dir as
we did before. But that's another step during setup.
So given that I have to recreate my workspaces on average once every
week, I object to the objections to having Eclipse files in the repo :-)
Andrus
P.S. oh, and BTW, JRE_LIB_15 is gone since yesterday, so a vanilla
Eclipse installation works with
On Aug 2, 2006, at 7:24 PM, Kevin Menard wrote:
This is another argument for not having the eclipse files in the
repo.
Unfortunately that would be ignoring the problem, not solving it.
Well, would using the eclipse plugin generate project files that work
properly for the caller's environment? I use the IDEA plugin on
another
project and it does.
--
Kevin
