| Re: [platform-ui-dev] Smart Import concerns |
|
On 05/30/2016 12:22 PM, Max Rydahl
Andersen wrote:
On 15 May 2016, at 22:33, Stefan Oehme wrote:I had a chat with Stefan and we'll consider new methods in the API to better support such case. No.What we talked about a while back was that once a detector stated it can identify a project the *detector* should do the import, not smart import itself to exactly allow things like m2e and more complex future buildship to "take over" the import. What you're suggestion would be more like an ability to filter which import wizards are visible according to the input folder. The idea behind the importer is really to provide a unified interface (both in term of API and UI) to allow a straightforward and consistent import across the variety of project types. With feedback from Stefan and compared to m2e, the importer interface will provide the ability to give more control to the contributing strategies. Actually, there are already ways for BuildShip and other to "take over" parts of import (they can run some specific import operation, even creation of project with virtual folders) as part of the Projectconfigurator interface, but all those currently feel like hacks. We need to make it more accessible and explicit in the API. |