[
https://issues.apache.org/jira/browse/FELIX-1324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12730403#action_12730403
]
David Savage commented on FELIX-1324:
-------------------------------------
Not so much, it's more about being able to launch and debug felix from eclipse.
Basically eclipse has the notion of Launch Configurations of which you can
supply our own factories. The factory does the job of abstracting the launch
away from just java static void main and allows you to configure more domain
specific stuff. A general purpose OSGi launch configuration would likely launch
felix (or other OSGi frameworks) via the rfc 132 launch api?
At runtime we used to have the ability (via newton) to install bundles directly
from the IDE including setting up source for things like debug break points
etc. In our newton integration this involved poking the OSGi container via a
JMX interface. It might be interesting to try to combine this with some of ssh
connection via gogo or potentially via the jmx integration in karaf?
Not sure haven't thought about this second part completely - happy to discuss
options etc.
> Add support for runtime debug/launch of felix via eclipse
> ---------------------------------------------------------
>
> Key: FELIX-1324
> URL: https://issues.apache.org/jira/browse/FELIX-1324
> Project: Felix
> Issue Type: New Feature
> Components: Sigil
> Reporter: David Savage
>
> Sigil previously had the ability to launch and debug a Newton OSGi container.
> This has been removed in the port to apache as it brought in dependencies on
> a product that was not compatible with the apache licence.
> Should be possible to rebuild this using existing felix tools
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
