Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 312233 - feature request - import project wizard on local repos
Summary: feature request - import project wizard on local repos
Status: CLOSED WONTFIX
Alias: None
Product: EGit
Classification: Technology
Component: Core (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: 0.8.0   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-05-10 06:36 EDT by Matthias Vach CLA
Modified: 2010-06-09 07:55 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Matthias Vach CLA 2010-05-10 06:36:26 EDT
Build Identifier: 

After importing a git repository, I would like to import the included projects via the git repositories view. Currently it is only possible to import standard eclipse projects but e.g. no maven projects.

It would be cool to find the standard import project dialog in the context menu which opens by right clicking: <repo> -> Branches ->Local Branches -> <branch>

Reproducible: Always
Comment 1 Mathias Kinzler CLA 2010-05-11 05:25:05 EDT
I have actually already tried to offer this before. Unfortunately, when starting the "Import Projects" wizard from another wizard context, the list of wizards is empty. I'll try to investigate why that happens.
Comment 2 Mathias Kinzler CLA 2010-06-09 07:55:42 EDT
Well, bad news: I managed to get the "Import Projects" wizard started from the Git wizard and it's possible to use it. However, both use cases that I tried (importing plug-ins from a directory and importing exsting maven projects using the sonatype plug-in) turned out to do the actual project creation asynchronously.
Consequently, after the "Import Projcts" wizard returns, the Git wizard will not detect the newly created projects correctly (since they are still being imported and created in the background), so more likely than not, sharing of the imported projects will fail or be incomplete.
The other issue here is that the import wizard expects some sort of workbench selection to be provided. This selection is forwarded to the acutal specific wizard and is helpful for providing context there. Since we are just in the business of creating projects, there is no meaningful selection that can be provided by the Git wizard.
Both these issues result in pretty bad usability.
The suggestion would be to use the "Import Projects" wizard normally, i.e. not from within the Git wizard and share the imported projets manually afterwards.