Re: [m2e-dev] Wish to contribute an incubating bundle for easier import

[Fred Bricon <fbricon@xxxxxxxxx>]

You perfectly explained why it was necessary to have these pom parents imported as projects :-)

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.

Take this as an example : http://screencast.com/t/ls1In7Uq

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.

On Mon, Mar 23, 2015 at 8:37 AM, Mickael Istria <mistria@xxxxxxxxxx> wrote:

On 03/23/2015 01:05 PM, Max Rydahl Andersen wrote:

Why would you not want parent pom projects to be available in eclipse ?

Because they don't provide any added value AFAIK.
It's meaningful to have a project (instead of a folder) when the edition of files inside this project requires "shared" data that is attached to the project (such as classpath containers, builders). But when you don't have any of these, it becomes useless (and resource consuming) to have an Eclipse project.
Take as example a package with type "eclipse-repository" and a category.xml in it. Category editor works well since it uses the workspace-scoped target-platform, so it doesn't store any project-wide data, and it's totally fine to edit it directly without turning the folder as a project.

--
Mickael Istria
Eclipse developer at JBoss, by Red Hat
My blog - My Tweets

_______________________________________________
m2e-dev mailing list
m2e-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/m2e-dev

--

"Have you tried turning it off and on again" - The IT Crowd