Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 339406

Summary: Unify Import Wizards
Product: z_Archived Reporter: Matthew Piggott <matthew>
Component: m2eAssignee: Matthew Piggott <matthew>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: P3 CC: pascal
Version: unspecified   
Target Milestone: ---   
Hardware: PC   
OS: Windows 7   
Whiteboard:

Description Matthew Piggott CLA 2011-03-09 13:23:23 EST 
The import wizard in m2e should really be combined.  The main difference between Import and Import from SCM is that we don't allow changing the import location when importing from SCM.

Currently both the wizards and their pages are nearly duplicates of each other.  Ideally we should use the same for both.
Comment 1 Matthew Piggott CLA 2011-03-14 15:04:15 EDT 
I didn't look close enough at the code when writing the bug, ProjectImportWizard was actually used in SCM import when no maven projects exist, but Eclipse projects do.  We can still remove the page, the typical Eclipse import is API as of 3.5.
Comment 3 Denis Roy CLA 2021-04-19 13:25:33 EDT 
Moved to https://github.com/eclipse-m2e/m2e-core/issues/