|
On 03/23/2015 02:23 PM, Fred Bricon
wrote:
Because the Maven builder is attached to them and because
Maven projects use pom inheritance, any change to the parent
pom can be automatically detected and applied to its modules.
There can be resource listener at other locations than under project
root.
changing the compiler version at the parent level triggers
classpath update to its java modules. Works the same for
dependency management. That couldn't happen if the parent pom
was not imported as a project.
For this use-case, it seems like you have a single level of
hierarchy, but when you have 2 levels of hierarchy (such as typical
Eclipse PDE projects that have bundles/ features/ and so on), I
don't see any value for the user to have the intermediary folders
shown as projects in IDE.
As a Maven/PDE user, I typically want my parent project as root of
the Project Explorer, and my modules loaded as projects to get
completion/validation/build. Intermediary folders are just there for
structuring purpose and I put a pom in them because it's the
convention. It doesn't mean I'll need them to be editable projects
in my IDE.
|
