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

[Anton Tanasenko <atg.sleepless@xxxxxxxxx>]

I can see logic in not importing projects with poms that aren't needed in eclipse build (eclipse-repository, eclipse-product), but you can never know which poms are needed and which not.

Not providing ways to import them in this general importer will alienate users which need that (myself included - I have a number of 'pom' projects that actually end up as eclipse java projects).

You could take the best of both worlds by providing an optional choice wizard page, where one could uncheck such projects, if needed.

2015-03-23 16:02 GMT+02:00 Mickael Istria <mistria@xxxxxxxxxx>:

On 03/23/2015 02:53 PM, Fred Bricon wrote:

Something tells me the deep level hierarchy with dummy intermediary poms in use in *some* PDE projects is not representative of the vast majority of Maven use cases.

Maybe the problem is the universal importer being to eager. It should allow users to choose which folders to imports as projects.

Choice is the enemy of usability ;) If it's going to ask complex questions again, let's just not do a new wizard and keep the current ones.
People who are advanced enough with m2e to know what to turn into a folder and what not can deal with it by themselves. So if you all agree that it's best to import all folders with a pom.xml as projects, I can change the code to do it. PDE users with intermediary poms will have to deal with that (either keep intermediary projects, or rework their poms, or remove intermediary projects and disable m2e on those projects).

--
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

--

Regards,

Anton.