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

Bug 367832

Summary:	Import with new project name not possible
Product:	[Technology] EGit	Reporter:	Dani Megert <daniel_megert>
Component:	UI	Assignee:	Project Inbox <egit.ui-inbox>
Status:	NEW ---	QA Contact:
Severity:	normal
Priority:	P3	CC:	kim.moir, robin.rosenberg, tomasz.zarna
Version:	1.2
Target Milestone:	---
Hardware:	All
OS:	All
Whiteboard:

Description Dani Megert

2012-01-04 06:22:15 EST

1.2.

In CVS one can use 'Check Out As...' to load a project into the workspace under a different name. This is currently not possible with Git:

- 'Import existing projects' does not allow to override the name

- 'Use the New Project Wizard' is useless (see bug ).

- 'Import as general project' does not work because it complains when there's
  already a '.project' file.


The simplest fix would be to lift the restriction from option 3.


This is a major issue for us because we can no longer import some of the projects after the Git migration (as it would result in duplicate names).

Comment 1 Dani Megert

2012-01-04 06:39:13 EST

> - 'Use the New Project Wizard' is useless (see bug ).

Bug 367833 that is.

Comment 2 Robin Rosenberg

2013-05-26 18:04:00 EDT

> ...we can no longer import some of the
> projects after the Git migration (as it would result in duplicate names).

This a limitation on Eclipse. It should allow the import with some warnings and automatic rename, like name(2) or something, so one can the fix it after import. It would be reasonable to expect such workspaces to be unbuildable until the issues have been resolved.

> - 'Use the New Project Wizard' is useless (see bug ).

This depends on the project type. It works for general projects, but not
many others.

>- 'Import as general project' does not work because it complains when there's
  already a '.project' file.

Platform limitation, I think.

Comment 3 Dani Megert

2013-05-29 10:43:11 EDT

(In reply to comment #2)
> > ...we can no longer import some of the
> > projects after the Git migration (as it would result in duplicate names).
> 
> This a limitation on Eclipse. It should allow the import with some warnings
> and automatic rename, like name(2) or something, so one can the fix it after
> import. It would be reasonable to expect such workspaces to be unbuildable
> until the issues have been resolved.
> 
> > - 'Use the New Project Wizard' is useless (see bug ).
> 
> This depends on the project type. It works for general projects, but not
> many others.
> 
> >- 'Import as general project' does not work because it complains when there's
>   already a '.project' file.
> 
> Platform limitation, I think.

The CVS importer can do this, so, saying it's a platform limitation isn't really true.

Comment 4 Dani Megert

2013-08-07 08:42:11 EDT

(In reply to comment #3)
> The CVS importer can do this, so, saying it's a platform limitation isn't
> really true.

See https://bugs.eclipse.org/bugs/attachment.cgi?id=234147