[ https://issues.jboss.org/browse/JBIDE-20365?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-20365: ---------------------------------------- Do you know some realistic user-stories to illustrate each one of your points, with example project and why each of this option seems necessary? About 1, it's going to be supported, but with some limitations. Indeed for some "strategies", the type of the parent may strongly impact how children are imported (for example, you don't want to import a folder that contains a .project if it's in the test data of an Eclipse test plugin), so there will be some limitation. However, the common case of a pure Maven project should work fine and make suggestions before running the import. About 2, I don't believe users really want that. What they want is something that "just" works without tweaking. Also, it's doing more that setting natures, and leaving the ability to user to override some detection is also giving them ability to do wrong things that would leave them in a very worse state. But I do agree that ability to change project natures is interesting, but I don't think it's something that should be necessarily done at import. IMO, it's just something the IDE should provide at anytime. This is the story of Eclipse bug https://bugs.eclipse.org/102527 ; I've implemented a simple way to tweak natures without editing .project: https://github.com/jbosstools/jbosstools-playground#naturist-edit-project... . I believe this approach of 1st import, then see projects in actions, and then tweak them if necessary better matches user workflow. About 3, that is planned and I'm working on it right now. However, it will probably have some limitations, similarly to 1. -- This message was sent by Atlassian JIRA (v6.3.15#6346)