I finally found the way to attach the source to the bundle in eclipse
pde. The trick is to add a header to the manifest.
This is what I added to the Manifest of the camel-core source bundle to
make it work in eclipse:
Bundle-SymbolicName: org.apache.camel.camel-core.source
Eclipse-SourceBundle: org.apache.camel.camel-core;version="2.2.0"
An explanation can be found in the eclipse pde faq:
http://wiki.eclipse.org/PDE/FAQ#How_do_source_attachments_for_bundles_work
I think this should be added to the standard camel build so I created a
jira issue for it:
https://issues.apache.org/activemq/browse/CAMEL-2734
Greetings
Christian
Am 18.05.2010 09:17, schrieb Christian Schneider:
Hi all,
while trying to get camel running in osgi I would like to be able to
debug through the source code in eclipse. When I am not using osgi I
usually leave the task of attaching the source to maven which does a
great job here.
For osgi I have set up a target platform where I copied the camel jars
and also the source jars from the maven repo. The problem is though
that the source is not resolved and there is no setting to tell
eclipse how to do it.
The source for the eclipse bundles is resolved so I guess it has to do
with the fact how the source is bundled.
Is there any way to use the sources from maven in eclipse plugin
dependencies? If not then I think it would be great to setup the camel
build in such a way that the source is bundled in a way that works in
eclipse plugin dependencies. Is this possible?
Gereetings
Christian
--
----
http://www.liquid-reality.de
