Dear developers,
Have you tried this:
$ cd branches/wicket-1.x/wicket-parent
$ mvn -Pjdk1.4 eclipse:eclipse
Or in trunk:
$ cd trunk/wicket-parent
$ mvn eclipse:eclipse
By default, maven-eclipse-plugin will use project references,
which means you will have your projects within the workspace.
***This will only work if you run Maven from the parent module***.
Now, with that command, there is no valid reason for keeping
.classpath and .project files in the Subversion repository
anymore. So please check that it works for you, and let's remove
the damned Eclipse files.
Previous discussions[1] have shown that there is no consensus for
what the .classpath files should contain, so the best is to just
let everyone manage that outside of the repository.
--
Jean-Baptiste Quenot
aka John Banana Qwerty
http://caraldi.com/jbq/
[1]
http://www.nabble.com/Re%3A-svn-commit%3A-r485805----incubator-wicket-branches-wicket-1.x-wicket-examples-.classpath-tf2814978.html
