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

Bug 440043

Summary: Eclipse cannot find Orion source code at debug time
Product: [ECD] Orion Reporter: Mark Macdonald <mamacdon>
Component: RelengAssignee: Project Inbox <orion.releng-inbox>
Status: RESOLVED WORKSFORME QA Contact:
Severity: normal    
Priority: P3 CC: ahunter.eclipse, maciej.bendkowski
Version: 5.0   
Target Milestone: ---   
Hardware: PC   
OS: Windows 7   
Whiteboard:

Description Mark Macdonald CLA 2014-07-21 16:12:32 EDT 
Eclipse does not associate Orion source files with breakpoints when debugging. Anthony and I have both encountered this. I'm using Kepler SR2 (20140224-0627), and Anthony is using Luna GA.


1. Launch Orion from Eclipse SDK using web-ide.launch
2. Pause execution at a breakpoint in one of the Orion server bundles.
3. The source code for these bundles is in the workspace, but JDT doesn't find it.


This can be worked around by clicking "Edit Source Lookup Path..." and browsing to the bundle that contains the code. But this is annoying because:
 i) It has to be done again for each project
ii) It modifies a tracked file (web-ide.launch) so it's liable to get committed by accident or overwritten
Comment 1 Maciej Bendkowski CLA 2014-07-22 04:19:54 EDT 
I had the same issue while using Kepler. After switching to Linux with Eclipse Luna (official release) I haven't encountered this problem.
Comment 2 Anthony Hunter CLA 2014-07-22 09:57:02 EDT 
(In reply to Maciej Bendkowski from comment #1)
> I had the same issue while using Kepler. After switching to Linux with
> Eclipse Luna (official release) I haven't encountered this problem.

I also have this issue and it is ironic that I thought I hit this issue when I switched from Kepler SR2 to Luna on my Linux box.
Comment 3 Mark Macdonald CLA 2014-07-22 11:42:40 EDT 
Yesterday after I opened this bug, I updated Eclipse from Kepler to Luna. That did not fix the problem.

Today, I restarted Eclipse, reloaded the target platform, and switched to an Oracle JRE. At this point I ran Orion and the problem was fixed. I then switched back to the IBM JRE, and the problem was still fixed.

So everything is fine now, although I have no idea what happened.
Comment 4 John Arthorne CLA 2015-05-08 09:49:58 EDT 
Working now.