| Source lookup doesn't work when debugging a fragment [message #331324] |
Mon, 01 September 2008 14:50  |
Eclipse User |
|
|
|
Originally posted by: jamesblackburn+eclipse.mac.com
Hi All,
I've created a fragment which overrides existing platform functionality.
I've added the fragment's jar to the plugin's Bundle-ClassPath and
Eclipse-ExtensibleAPI: true
The code builds and runs as expected - I can verify that my code is
being called. However if I set a breakpoint, the source shown is for
the original plugin, not the fragment (line numbers etc. are out of whack).
In the Debug View's Source Lookup path, the Default grouping shows the
plugin before the fragment. If I remove the default grouping and add
<plugin>.patch before <plugin> I still get the Plugin's source instead
of the fragment's...
Am I doing something wrong or should I file a bug?
Cheers,
James
|
|
|
| Re: Source lookup doesn't work when debugging a fragment [message #331326 is a reply to message #331324] |
Mon, 01 September 2008 16:25  |
| Eclipse User |
|
|
|
Originally posted by: zx.code9.com
James Blackburn wrote:
> Hi All,
>
> I've created a fragment which overrides existing platform functionality.
> I've added the fragment's jar to the plugin's Bundle-ClassPath and
> Eclipse-ExtensibleAPI: true
>
> The code builds and runs as expected - I can verify that my code is
> being called. However if I set a breakpoint, the source shown is for
> the original plugin, not the fragment (line numbers etc. are out of whack).
>
> In the Debug View's Source Lookup path, the Default grouping shows the
> plugin before the fragment. If I remove the default grouping and add
> <plugin>.patch before <plugin> I still get the Plugin's source instead
> of the fragment's...
>
> Am I doing something wrong or should I file a bug?
Can you file a bug for this, this could be an issue with the new source
bundle story.
Thanks!
Cheers,
~ Chris
|
|
|
| Re: Source lookup doesn't work when debugging a fragment [message #331327 is a reply to message #331326] |
Mon, 01 September 2008 16:52 |
| Eclipse User |
|
|
|
Originally posted by: jamesblackburn+eclipse.mac.com
Chris Aniszczyk wrote:
> James Blackburn wrote:
>> Hi All,
>>
>> I've created a fragment which overrides existing platform
>> functionality. I've added the fragment's jar to the plugin's
>> Bundle-ClassPath and Eclipse-ExtensibleAPI: true
>>
>> The code builds and runs as expected - I can verify that my code is
>> being called. However if I set a breakpoint, the source shown is for
>> the original plugin, not the fragment (line numbers etc. are out of
>> whack).
>>
>> In the Debug View's Source Lookup path, the Default grouping shows the
>> plugin before the fragment. If I remove the default grouping and add
>> <plugin>.patch before <plugin> I still get the Plugin's source instead
>> of the fragment's...
>>
>> Am I doing something wrong or should I file a bug?
>
> Can you file a bug for this, this could be an issue with the new source
> bundle story.
>
> Thanks!
Thanks for the reply Chris, I've filed https://bugs.eclipse.org/245893
Interestingly source lookup does work when the class only exists in the
fragment (using either source lookup path of 'Default' or
<plugin>.patch, <plugin>) but still can't convince the thing to show me
the correct class when the it exists in both the fragment and the plugin.
Cheers,
James
>
> Cheers,
>
> ~ Chris
|
|
|
Powered by
FUDForum. Page generated in 0.02877 seconds
] 
Search
Help
Register
Login
Home
