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

Bug 344485

Summary:	Import Projects from Repository: Locations mapping dialog not always shown
Product:	[Eclipse Project] Platform	Reporter:	Markus Keller <markus.kell.r>
Component:	Team	Assignee:	Platform Team Inbox <platform-team-inbox>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	normal
Priority:	P3	CC:	curtis.windatt.public, daniel_megert, pwebster
Version:	3.7
Target Milestone:	---
Hardware:	All
OS:	All
Whiteboard:	stalebug

Description Markus Keller

2011-05-02 12:20:43 EDT

I20110428-0848

- new workspace
- try to import project org.eclipse.compare from repository
=> dialog that asks for user name / password

Expected: The "Specify Repository Information" dialog that allows me to select an existing repository connection or create a new one.

This dialog already appears when the workspace already contains another repository connection (doesn't even have to be a compatible one!). It only doesn't appear out of the box when I try to import my first project.

BTW: The info message at the top of the dialog is wrong. It says:
"The project set only contains partial repository information. You may use the table below to specify the complete repository information for each repository in the project set or click OK to use the default repository location."

=> I'm not importing project sets.
=> The same dialog also appears when the information is not partial, e.g. when I hack the Eclipse-SourceReferences property in org.eclipse.jdt.debug's MANIFEST.MF to include the "anonymous@" user name (which should be changed anyway, see bug 344483).

Comment 1 Curtis Windatt

2011-05-02 15:51:45 EDT

Moving to TEAM.

Not sure if there is anything that can be done here as partial repo information is included with the source bundle.

The import runs the same code as a project set file, I assume that is why the name of wizard uses the project set.

Comment 2 Dani Megert

2011-05-03 06:23:44 EDT

See also bug 326740.

Comment 3 Lars Vogel

2019-11-14 02:13:54 EST

This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

If the bug is still relevant, please remove the "stalebug" whiteboard tag.