Valerio Schiavoni wrote:
Hello Max,
Max Cooper wrote:
If you have a structure like this:
root
|--module1
|--module2
|--submodule2-1
my structure is a bit simpler, without nested submodules.
Okay, like this:
root
|--module1
|--module2
Max Cooper wrote:
... you would have to make sure that you hide/delete/rename the .project
file in both the root and module2 directories for the submodule2-1
project to show up on the import.
so fortunately this is not my case.
Generally, this still is the case. You MUST hide/delete the .project
file in root so that Eclipse will allow you to add module1 and module2.
It is the same issue, but you only have to worry about one level.
I have verified that the procedure outlined in this email thread works
in Eclipse 3.2, as have others. If it isn't working for you, something
is wrong.
Max Cooper wrote:
Eclipse does not support hierarchical project structures.
i thought eclipse 3.2 just introduced this new feature ...
Eclipse 3.2 does not support hierarchical project hierarchies. It was
rumored that 3.2 would have such support before the release, but it does
not.
The procedure in this email thread is just a trick to get Eclipse to
accept having "overlapping" projects. This trick allows a hierarchical
structure of Maven modules to be mapped into a flat structure of Eclipse
projects.
Max Cooper wrote:
IMO, moving your parent pom to a subdir is a better compromise than
having all of your files show up two or more times in Eclipse.
of course, but this would break a well established maven convention, which
i'd like to avoid..
Moving the parent to a subdir is documented on the Maven site, and many
people are using this technique successfully.
The Eclipse trick in this thread is not as clean, IMO.
-Max
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
