My use case if that I may have shared the whole Gradle multiproject in the SCM, so if a member of the software development team will check it out, he will find it fully configured already.
Ideally, the standard Eclipse "Import => File system => Existing project into workspace" would be enough, but it has the problem that it can't handle Gradle multiprojects correctly (especially if the master project is stored in the root of the physical structure of the multiproject).
So, what I would need here is the following:
- provide a checkbox to "import and do nothing" (you call it "hands off")
- if that checkbox is NOT checked, individual checkboxes should be available to let the user choose what he/she wants the import wizard to perform; all these check boxes may be checked by default
IMHO, the "run before", "run after" and "create resource filters" could also be moved into this group of checkboxes, because their semantic is the same (i.e.: do some processing to set up the imported Eclipse project).
I would also add the following. The "run before" and "run after" features are great if you want to add the execution of custom tasks before and after the import. However, since the standard tasks the wizard proposes (cleanEclipse and eclipse in "before" and afterEclipseImport in "after) are probably standard actions that a user should accept most of the times (except for the "hands off" use case), they should probably be better handled by dedicated checkboxes, while leaving the edit box for "run before" and "run after" empty for the user to add only custom behaviour. Moreover, these check boxes for executing "cleanEclipse", "eclipse" and "afterEclipseImport" tasks may have a label (or at least a tooltip) that explains the user what they do to the project, rather than what tasks they will execute. In fact, from an Eclipse user point of view, it's not clear what will happen if I let the import wizard run those tasks or not, unless I go to the Gradle website and I read the documentation....