Bug 354524 – Add an "Import Project Strategy" extension point to the Import Project Wizard

Bug 354524 - Add an "Import Project Strategy" extension point to the Import Project Wizard


Summary:	Add an "Import Project Strategy" extension point to the Import Project Wizard

Status:	NEW

Product:	EGit
Classification:	Technology
Component:	UI
Version:	unspecified
Hardware:	All All

Importance:	P3 enhancement with 2 votes (vote)
Target Milestone:	---
Assigned To:	Project Inbox
QA Contact:

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:
	Show dependency tree

Reported:	2011-08-11 12:22 EDT by Fred Bricon
Modified:	2014-10-07 06:14 EDT (History)
CC List:	5 users (show)

See Also:	428089

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 Fred Bricon

2011-08-11 12:22:26 EDT

Hi,

Current Import project wizard allows a user to select what kind of import should be performed after the git setup : Existing project, New Project Wizard, General Project.

m2e has its own "import from git" wizard (https://github.com/sonatype/m2eclipse-egit), but offers much more limited capabilities (can't select branch, initial branch, remote name ...)

Snjezana Peco wrote an "Import Maven Projects from Git" wizard based off the existing eGit wizard : http://community.jboss.org/people/snjeza/blog/2011/02/28/how-to-work-with-seam-3-examples-using-jboss-tools-m2eclipse-and-egit
 
But ideally, we'd like to see this "Import as Maven project" option directly integrated into the existing eGit wizard. So, IMHO, an interesting approach would be for the eGit ui plugin to provide some hooks to add different import strategies. That way, m2e, JBossTools or any other interested party could easily contribute new ways to configure projects imported from git.

What do you think?

Comment 1 Mickael Istria

2014-02-13 07:34:09 EST

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!)

Comment 2 Mickael Istria

2014-10-07 06:14:29 EDT

Another possible import strategy: the "guess what" import strategy available in https://github.com/mickaelistria/jbosstools-eclipse#easy-openimport-of-a-project