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

Bug 315126

Summary: First scrapbook evaluation attempts to display source
Product: [Eclipse Project] JDT Reporter: Darin Wright <darin.eclipse>
Component: DebugAssignee: JDT-Debug-Inbox <jdt-debug-inbox>
Status: NEW --- QA Contact:
Severity: normal    
Priority: P3 CC: baptiste, sarika.sinha
Version: 3.6Keywords: helpwanted
Target Milestone: ---   
Hardware: PC   
OS: Windows XP   
Whiteboard: stalebug

Description Darin Wright CLA 2010-05-31 14:50:57 EDT
3.6 RC3

* Create a new scrapbook file (.jpage) in the Java perspective
* Enter "System.out.println("something");"
* Evaluating the text (exeucute, display, or inspect)
* A "Source not found" editor appears (*should not*)
* Close the editor
* Re-evaluate the text
* Editor does not appear (*as expected*)
* Close/re-open the scrapbook page
* First evaluation again makes "Source not found" editor appear
* Terminating the page and re-evaluating also makes editor appear
Comment 1 Baptiste Grenier CLA 2011-02-18 07:54:43 EST
I was not able to reproduce this behaviour using helios.
Comment 2 Eclipse Genie CLA 2018-10-12 13:56:15 EDT
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.

--
The automated Eclipse Genie.
Comment 3 Sarika Sinha CLA 2018-10-17 01:45:24 EDT
I have faced this problem many time, should spend some time to fix this.
Comment 4 Eclipse Genie CLA 2021-12-06 15:23:31 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.

--
The automated Eclipse Genie.