Valentin Valchev created FELIX-5168:
---------------------------------------
Summary: source release of felix artifacts
Key: FELIX-5168
URL: https://issues.apache.org/jira/browse/FELIX-5168
Project: Felix
Issue Type: Improvement
Components: Main, Maven Bundle Plugin
Reporter: Valentin Valchev
Priority: Trivial
Currently there is a "sources" artifact generated for every bundle, that is
being released by the Felix community.
Those sources however are not quite useful, if you do not develop a "maven"
project.
I'm using Eclipse - it is probably the main OSGi developers tool. The typical
OSGi development model in Eclipse is to have a PDE project, which uses the
so-called "Target Platforms". And target platform is usually a folder with
bundles, and PDE resolves the dependencies manually.
If the sources are generated with bnd, using the <_sources> tag, they are
embedded in OSGI-OPT/src folder, inside the bundle. Those sources are
automatically detected by Eclipse.
However, if you generate a separate source bundle, Eclipse will be stupid
enough not to consider that "XYZ-sources.jar" is the sources for "XYZ.jar".
Instead it will expected that XYZ-sources.jar has a manifest entry
"Eclipse-SourceBundle: XYZ".
So, adding this header to the source releases will be great for all Eclipse PDE
developers.
--
Sorry, if I didn't set the correct component. I searched for Felix master POM,
but didn't found any results. I've also added Maven Bundle Plugin component,
because you guys probably also have an opinion on that matter.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
