Srepfler Srgjan wrote:

this was my original question that eclipse:eclipse only generates project files for each of the modules but not for the parent project. So I guess this would be a really nice feature.

Regards,
Ingo

When you say parent project are you referring to a multi module project? What would the equivalent of it be under eclipse, I mean it's not a project with a java nature, what is it? Also if such a feature would need to be implemented I believe the only way to achieve something like that would be to make a multi module projects but with a flat hierarchy (as eclipse can't handle projects that are within projects but all projects are flatly in a workspace) and relative paths between them and people on the list have been against that kind of approach (but don't ask me why). Anyhow, once you generate the projects for the modules and import them in the workspace, do you need the parent project? Only possible use I see if some maven plugin manages to run some targets on the parent pom, otherwise I don't know. Anyone?
Srgjan
Hi.

Yes, at least I was talking about a parent POM project. Eclipse could just create a "Simple Project" for these. The salient point is being able to mount the parent [root] directory to edit files and execute Maven on that POM from eclipse. Ingo's post points out that the latest Eclipse version does handle nested projects. This is the way I would prefer to work myself; with separate modules.

You can have Maven generate projects for the child modules by using mvn eclipse:eclipse on the parent POM. Then in eclipse create the parent project by hand -- and this could be a "Simple" project if you want. Then you can mount any or all projects separately; and you can now execute Maven on the parent POM from within eclipse, not to mention also edit that POM and any other parent-level artifacts. You might have quite a bit in there like SCM, site, Javadoc, assemblies, filters, etc.

Of course, as was mentioned, you need eclipse 3.2 to get this support for nested projects. It is currently at version RC4. There seem to be one or two quirks, but from my perspective nothing seemed major -- I use the JDK tools as the compiler etc, so I so happen to avoid any issues that might exist there: YMMV with beta software.

Hope that helps.

- Steven.

Reply via email to