Re: [platform-ui-dev] Smart Import concerns

[Mickael Istria <mistria@xxxxxxxxxx>]

On 05/15/2016 10:33 PM, Stefan Oehme wrote:

We use what the user tells us and de-duplicate by prepending the parent names if there is a clash.

That strategy would actually be a better one for the importer as well.
I've opened https://bugs.eclipse.org/bugs/show_bug.cgi?id=493716 to track this idea.

How do you do it at once? As far as I saw the API has a per-project callback and says "these methods should be stateless". If there is some hook for "Configure all of these in a batch", then that would work for Buildship.

Using static objects (the cause and solution of many problems ;). See https://github.com/eclipse/m2e-core/blob/master/org.eclipse.m2e.importer/src/org/eclipse/m2e/importer/internal/MavenProjectConfigurator.java#L258 .

- Buildship gives you folders + the project names they should have

- You import each of those folders with the desired name

- Some folders might not exist yet, so you create them for us if the user selects them

- There is some way for Buildship to "collect" all the projects it needs to configure and to know when all of them are "ready to be configured" in one big batch.

Does that sounds reasonable?

Yes it seems very reasonable.

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