Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 341047 - import wizard does not preselect workspace basedir
Summary: import wizard does not preselect workspace basedir
Status: RESOLVED FIXED
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: m2e (show other bugs)
Version: unspecified   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-03-26 19:39 EDT by Igor Fedorenko CLA
Modified: 2021-04-19 13:22 EDT (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Igor Fedorenko CLA 2011-03-26 19:39:01 EDT 
Underlying user story... My workspace has a multi-module maven project, with agregator and modules all represented as separate workspace projects. I update the source tree from SCM, which pulls new maven module projects as subdirectories of the aggregator project on filesystem. In order to import these new projects, I was to be able to right-click on the aggregator, open maven import wizard and have the import wizard appear with basedir and all modules pre-populated. Alternatively, I want to be able to right-click on individual module folders and have the import wizard appear prepopulated with these modules and their submodules.

I believe this is very common usage pattern and needs to be fixed.
Comment 2 Denis Roy CLA 2021-04-19 13:22:24 EDT 
Moved to https://github.com/eclipse-m2e/m2e-core/issues/