|Maven and Eclipse: there is no way to import the glassfish projet (100's of modules) using Eclipse. [message #873261]
||Thu, 17 May 2012 20:33
| Grunt Grunt
Registered: December 2009
The Glassfish project is an open source project made of hundreds of maven modules.
The organization of these modules is made a way that neither a mvn eclipse:eclipse + Import Projects, nor a m2eclipse installed + Import existing Maven Projects can import all the projects successfully.
For example, among them you will find an artifactId of some name used in two or three differents groupId. Which is legal with Maven, of course.
This, mvn eclipse:eclipse cannot manage, because it names the eclipse projects generated from those modules with the artifactId they have, and this artifactId only. This causes duplicates during importation, making Eclipse ending it quickly.
the eclipse:eclipse plugin should be able to name the projects imported with [groupId].[artifactId] instead. But this feature is no more working since the 2.6 version of this plugin, and we are today on the version 2.9 of this plugin (which, I guess, is currently dying).
The second trouble Eclipse encounters inside the Glassfish modules is that they are not flatted like the Eclipse expect them in a workspace, but they are set in a hierarchical structure:
And this, for his part, m2eclipse cannot handle.
m2eclipse doesn't search for Maven projects in the subdirectories of C module, for instance, and thus, doesn't create the required .project, .classpath for these submodules.
The end of this story, is that no Maven eclipse plugin is able to handle the Glassfish project, because its organisation is:
- not well understood by m2clipse.
- not well handled by eclipse:eclipse.
The consequence? To enter the Glassfish project in order to view a source file, search an explanation for a bug or submit an feature, you have to use Netbeans and not Eclipse. And Netbeans is not the IDE I want to use.
But what? We are in 2012 now. When shall we expect having a true, native and flawless support of Maven projects and modules by Eclipse? Shall we wait 2018?
Maven projects are often hierarchical.
Eclipse should now be able to handle perfectly a hierachical structure of projects.
But well, one job after other:
Does anyone know the procedure that allows to import all the glassfish modules of the Glassfish project into Eclipse?
You can checkout the glassfish project doing an:
and attempt to import it to Eclipse (you are succesful, of course, when no more problems are listed in the Problems view).
But be warned: it's a big challenge!
[Updated on: Thu, 17 May 2012 20:47]
Report message to a moderator
Powered by FUDForum
. Page generated in 0.01695 seconds