[
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_2.zip
FYI, the previous example was generated from Pax-Construct and tweaked to use
only the bundle and dependency plugins - the original example generated using
Pax-Construct 0.2.1-SNAPSHOT is here.
To generate the Eclipse PDE files, use "mvn clean pax:eclipse"
BTW, to create this example I used the following Pax-Construct commands:
pax-create-bundle -p org.example
cd org.example
pax-embed-jar -a junit -v 3.8.1
(I added a ref to the junit class in the activator to check it compiled ok)
For more information about Pax-Construct, see the wiki:
http://wiki.ops4j.org/confluence/x/8Q
and the current documentation for 0.2.0:
http://www.ops4j.org/projects/pax/construct
> 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.
