[
https://issues.apache.org/jira/browse/FELIX-397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stuart McCulloch updated FELIX-397:
-----------------------------------
Attachment: EMBED_EXAMPLE.zip
Example of using the snapshot maven-bundle-plugin with the
maven-dependency-plugin to create the necessary files for Eclipse PDE: uses
manifestLocation to put the generated manifest in the top folder and
Embed-Directory/Embed-StripGroup to match the Bundle-ClassPath entries with the
locations used by the dependency plugin.
Use 'mvn clean eclipse:eclipse -Declipse.pde install' to generate the PDE
metadata and manifest.
(install must be after eclipse:eclipse, otherwise a bug in the
maven-eclipse-plugin will corrupt the manifest by adding a bogus empty line)
> 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
>
>
> 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.
