[
https://issues.apache.org/jira/browse/FELIX-397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12539002
]
Stuart McCulloch commented on FELIX-397:
----------------------------------------
You are correct that the *generated* manifest contains an absolute link in one
of the manifest entries - however this particular entry (Include-Resource) is
only used by the Bnd tool when assembling the bundle and will not affect use of
the bundle by other people. This entry is *not* used by Eclipse when importing
or deploying the bundle, or by the maven-eclipse-plugin.
The problem you see is an unrelated issue with the maven-eclipse-plugin, which
adds any dependent non-bundle jars as 'linked' files (see the generated
.project file for the actual link) when it runs in PDE mode. This causes the
problem in sharing the project, not the Include-Resource entry. ( Note if you
use the Pax-Construct tools this won't occur, as it extends the
maven-eclipse-plugin so that embedded jars appear with the correct M2_REPO
aliased entry in the .classpath file )
Secondly, while it may be convenient in some situations to have the
maven-bundle-plugin configure the maven-dependency-plugin, this is really
outside of the scope of the bundle-plugin and would negatively impact people
who don't use Eclipse and don't require such functionality. In these cases you
should either configure the plugins manually as explained above, or use
something which has been explicitly written to do this for you, such as the
Pax-Construct tools.
The strength of Maven comes from having small plugins that focus on a
particular task that can then be put together as required.
> Interoperability with Eclipse Equinox and PDE
> ---------------------------------------------
>
> Key: FELIX-397
> URL: https://issues.apache.org/jira/browse/FELIX-397
> Project: Felix
> Issue Type: New Feature
> Components: Maven Bundle Plugin
> Reporter: Eugene Kuleshov
> Attachments: EMBED_EXAMPLE.zip, EMBED_EXAMPLE_2.zip
>
>
> Maven bundle plugin can nicely collect all Maven dependencies, generate
> bundle manifest and create jar package. However it is not very useful if you
> need to run that bundle in self-hosted mode for debugging. Eclipse provides
> nice development and debugging environment for OSGi bundles, but bundles
> created by this plugin can't be easily used there.
> One possible option would be to provide a separate goal that would create
> folder structure compatible with Eclipse PDE. Basically place generated
> manifest file into the ${basedir}/META-INF/MANIFEST.MF and copy jars
> according to the Bundle-ClassPath attribute. Then such project could be
> imported into Eclipse and used with PDE.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
