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

Bug 326740

Summary: [Project Sets] Import Team Project Set wizard must allow to choose connection type
Product: [Eclipse Project] Platform Reporter: Dani Megert <daniel_megert>
Component: TeamAssignee: Platform Team Inbox <platform-team-inbox>
Status: CLOSED WONTFIX QA Contact:
Severity: normal    
Priority: P3 CC: grzegorz.abramczyk, markus.kell.r, pwebster, Szymon.Brandys, tomasz.zarna
Version: 3.6   
Target Milestone: ---   
Hardware: All   
OS: All   
Whiteboard: stalebug
Attachments:
Description Flags
demo team project set none

Description Dani Megert CLA 2010-10-01 03:31:37 EDT
R3.6.

1. start with new workspace
2. start to import attached team project set
3. click 'Finish'
   ==> password dialog comes up. Now assume you don't have commit rights i.e. 
       you can't connect via extssh
   ==> there's no way to continue from here as clicking 'OK' just brings the 
       same dialog back.
4. click 'Cancel'
   ==> even though I canceled the operation an invalid connection is created:
       :extssh:dev.eclipse.org:/cvsroot/eclipse
5. try to import again
   ==> now it is even worse: I can't even enter a user name anymore.


The password dialog should allow to choose the connection type and upon cancel we should remove the temporarily created repository.
Comment 1 Dani Megert CLA 2010-10-01 03:32:22 EDT
Created attachment 180016 [details]
demo team project set
Comment 2 Tomasz Zarna CLA 2010-12-22 07:09:26 EST
Gosia please take a look at this. iirc we already have a bug complaining about bogus CVS connections created when using the wizard, but I can't find it at the moment. It should be one of the bugs tagged with [Project Sets].
Comment 3 Szymon Brandys CLA 2011-03-29 09:10:28 EDT
Moving to 3.8.
Comment 4 Szymon Brandys CLA 2012-04-30 05:52:30 EDT
We most likely will not have time to work on that during 3.8 cycle.
Comment 5 Eclipse Genie CLA 2020-02-18 13:33:04 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. As such, we're closing this bug.

If you have further information on the current state of the bug, please add it and reopen this bug. 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.

--
The automated Eclipse Genie.