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

Bug 331989

Summary:

Edit... button in the "Workspace Cannot Be Locked" dialog does not show up in many cases

Product:

[Eclipse Project] PDE

Reporter:

Raksha Vasisht <raksha.vasisht>

Component:

Assignee:

PDE-UI-Inbox <pde-ui-inbox>

Status:

CLOSED DUPLICATE

QA Contact:

Severity:

normal

Priority:

CC:

daniel_megert, markus.kell.r

Version:

3.7

Target Milestone:

---

Hardware:

OS:

Windows XP

Whiteboard:

Attachments:

Description	Flags
Screenshot of the 'Plug-in Development' preference page	none
Screenshot of the launch configuration page	none

Description Raksha Vasisht

2010-12-07 04:36:41 EST

I20101206-1800

Steps:

1) Launch the above mentioned build with a fresh workspace
2) Do not modify any preferences , create a new eclipse application launch configuration and run it
3) Immediately run the same config again

=> I see the old error dialog and not the one with Edit... button on it.

Although I can never see this on my machine when I launch with JRE 1.5 or 1.6 , I saw this on another machine with similar PDE preferences (default) and JRE 1.5: 

4) Try to launch the second config after some delay (say a min). The new dialog appears immedialtely instead of the splash screen.

Ill attach the preference page (although its default settings and nothing was modified in both cases )

Comment 1 Raksha Vasisht

2010-12-07 04:40:06 EST

Created attachment 184694 [details]
Screenshot of the  'Plug-in Development' preference page

Comment 2 Raksha Vasisht

2010-12-07 04:42:27 EST

Created attachment 184696 [details]
Screenshot of the  launch configuration  page

Comment 3 Dani Megert

2010-12-07 04:44:46 EST

I see the same here. Looks like a timing issue. Why is the old dialog still around anyway?

Comment 4 Markus Keller

2010-12-07 06:33:15 EST

This is the same problem as bug 331992. The "old" dialog is not really the "old" one, but a similar one from the launcher.

*** This bug has been marked as a duplicate of bug 331992 ***