Eventually, I have installed [i]NetBeans 6.8[/i] to build [i]Glassfish[/i].
It has a far lower amount of features comparing to [i]Eclipse[/i] (especially options for Java formatting that are sparse), but it works.
I've left [i]Eclipse[/i] when [i]m2eclipse[/i] succeeding in importing [i]Glassfish[/i] projects,
but then [i]Eclipse[/i] considered them as [i]Maven[/i] projects instead of Java projects, and therefore was not able to declare some projects being some dependencies of others (to be more concrete: [i].project[/i] files could exist under subdirectories, but no [i].classpath[/i] files).
I ran the [i]Maven[/i] [i]eclipse:eclipse[/i] plugin, said to handle this problem. But if it created some files, I was astounded to discover that some [i].classpath[/i] files had for comment something like "[i]This file generated by mvn eclipse:eclipse is not compatible with m2eclipse.[/i]"!
As far as I know, [i]m2eclipse[/i] is the only plugin existing for handling [i]Maven[/i] under eclipse. So I was wondering what was the goal of all this work.
It was a bit too much for me.
[b][i]Eclipse 3.5[/i] is unable to handle [i]Maven[/i] properly.[/b] Maybe [i]Eclipse 3.9[/i] will be the version truely designed to manage Maven projects, not delegating this task to a plugin that is only a pain.
[Message sent by forum member 'grunt2000']
http://forums.java.net/jive/thread.jspa?messageID=396812