| debug opens .java instead of .class [message #23378] |
Wed, 24 September 2008 11:41  |
Eclipse User |
|
|
|
Originally posted by: ottrich.fast-mail.org
Hello,
I'm developing some OSGi-bundles and use maven as build tool. I provide
the source of the bundles as seperate source-bundles with the new
Eclipse-SourceBundle header in the source-bundle MANIFEST.MF.
Such a MANIFEST.MF looks like this:
Manifest-Version: 1.0
Bundle-ManifestVersion: 2
Bundle-Name: test.source
Eclipse-SourceBundle: test;version="1.1.0-SNAPSHOT"
Bundle-SymbolicName: test.source
Bundle-Version: 1.1.0-SNAPSHOT
This bundles are installed into a eclipse-targetplatform within the binary
jars.
Here is my problem:
when debugging my bundles, the .java files in the source-bundles-jars are
opened. But now I can't use the "inspect" operation and I can not navigate
through the source.
"Step into" and other things are working.
If I manually go to the .class-files under the plugin-dependencies and
open them, they behave like expected, except they are not opened by the
debugger-sourcelookup.
I thought that the .java-files should be "connected" with the binary
class-files.
Where is my mistake?
regards,
Lars
|
|
|
| Re: debug opens .java instead of .class [message #23464 is a reply to message #23378] |
Wed, 24 September 2008 14:45  |
| Eclipse User |
|
|
|
Originally posted by: zx.code9.com
Lars Fischer wrote:
> Hello,
>
> I'm developing some OSGi-bundles and use maven as build tool. I provide
> the source of the bundles as seperate source-bundles with the new
> Eclipse-SourceBundle header in the source-bundle MANIFEST.MF.
>
> Such a MANIFEST.MF looks like this:
>
> Manifest-Version: 1.0
> Bundle-ManifestVersion: 2
> Bundle-Name: test.source
> Eclipse-SourceBundle: test;version="1.1.0-SNAPSHOT"
> Bundle-SymbolicName: test.source
> Bundle-Version: 1.1.0-SNAPSHOT
>
> This bundles are installed into a eclipse-targetplatform within the
> binary jars.
>
> Here is my problem:
> when debugging my bundles, the .java files in the source-bundles-jars
> are opened. But now I can't use the "inspect" operation and I can not
> navigate through the source.
> "Step into" and other things are working.
>
> If I manually go to the .class-files under the plugin-dependencies and
> open them, they behave like expected, except they are not opened by the
> debugger-sourcelookup.
>
> I thought that the .java-files should be "connected" with the binary
> class-files.
>
> Where is my mistake?
Lars, can you file a bug with a small reproducible test case (against PDE)?
Some small bundle/source bundle would do.
This sounds like a bug with PDE's source lookup but I'm not sure yet.
Cheers,
~ Chris
|
|
|
| Re: debug opens .java instead of .class [message #23803 is a reply to message #23464] |
Thu, 25 September 2008 06:38 |
| Eclipse User |
|
|
|
Originally posted by: ottrich.fast-mail.org
Hello Chris,
Chris Aniszczyk wrote:
> Lars, can you file a bug with a small reproducible test case (against PDE)?
> Some small bundle/source bundle would do.
> This sounds like a bug with PDE's source lookup but I'm not sure yet.
I'm unfamiliar what to do for "against PDE". I created a simple bundle,
but I don't know how to create separate jars only with eclipse. I use
always maven for this.
I can manually create two example jars (binary and source) and share them.
Would this be ok?
regards,
Lars
|
|
|
| Re: debug opens .java instead of .class [message #24090 is a reply to message #23803] |
Thu, 25 September 2008 13:33 |
| Eclipse User |
|
|
|
Originally posted by: zx.code9.com
Lars Fischer wrote:
> Hello Chris,
>
> Chris Aniszczyk wrote:
>> Lars, can you file a bug with a small reproducible test case (against
>> PDE)?
>> Some small bundle/source bundle would do.
>> This sounds like a bug with PDE's source lookup but I'm not sure yet.
>
> I'm unfamiliar what to do for "against PDE". I created a simple bundle,
> but I don't know how to create separate jars only with eclipse. I use
> always maven for this.
> I can manually create two example jars (binary and source) and share
> them. Would this be ok?
Sure that's fine.
Cheers,
~ Chris
|
|
|
| Re: debug opens .java instead of .class [message #24798 is a reply to message #24090] |
Tue, 30 September 2008 08:02 |
| Eclipse User |
|
|
|
Originally posted by: ottrich.fast-mail.org
Hello Chris,
I created two bundles (A uses a class of B) build by maven and created the
binary and source jars.
1.) I copied the jars of B into a clean targetplatform of a clean
workspace and tried to debug it: everything works fine! The lookup opend
the .class file (Icon with "010").
2.) I copied the same jars of B into the targetplatform of my old
workspace and tried to debug it from my regular projects: the lookup opens
the .java file (icon with an unfilled bordered "J") and there I can't
inspect the variables, etc. :(
3.) I set up a new workspace, added our projects and settings, added Bs
jars and tried it again: debug is NOT working :(
Now I'm confused. I don't know how to provide an example of this
behaviour, because it is working in other environments but not in ours. I
can not share my workspace with my regular projects to the public. :(
We have a team of 5 members, all having the same problem.
I would be very happy about some hints.
This is our eclipse installation:
- eclipse classic (3.4.1)
- xml-tools (3.0.2)
- m2eclipse
- subversive
- spring-ide
- nothing special else
I can send more details if needed.
regards,
Lars
|
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.04880 seconds
] 
Search
Help
Register
Login
Home
