| Summary: | Add an "Import Project Strategy" extension point to the Import Project Wizard | ||
|---|---|---|---|
| Product: | [Technology] EGit | Reporter: | Fred Bricon <fbricon> |
| Component: | UI | Assignee: | Project Inbox <egit.ui-inbox> |
| Status: | NEW --- | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | adietish, manderse, mistria, sslavic, youngm |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| See Also: | https://bugs.eclipse.org/bugs/show_bug.cgi?id=428089 | ||
| Whiteboard: | |||
|
Description
Fred Bricon
See also bug 428089 which could be used to configure nature on an existing IProject. That could be used by EGit and other import scenarios to perform import in 2 steps: 1. Select location to import as project 2. Then apply various configurators for the given project IMO, this issue can be addressed at platform level (where patches and ideas are welcome!) Another possible import strategy: the "guess what" import strategy available in https://github.com/mickaelistria/jbosstools-eclipse#easy-openimport-of-a-project |