[
https://issues.apache.org/jira/browse/FELIX-397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12538989
]
Eugene Kuleshov commented on FELIX-397:
---------------------------------------
Thanks Stuart. This almost works.
Almost, because bundle plugin generates an absolute link to the local Maven
repository in MANIFEST,
Include-Resource:
target/dependency/junit-3.8.1.jar=C:\repo\junit\junit\3.8.1\junit-3.8.1.jar
such Eclipse project can't be shared across team members and require manual
steps before it can be imported to the ide.
It would be also more convenient if bundle plugin could copy required
dependencies without manual configuration of maven-dependency-plugin, that
would also help to match list of dependencies and target directory location
(won't have to duplicate that).
> 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.
