You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "David Savage (JIRA)" <ji...@apache.org> on 2009/07/13 15:43:17 UTC

[jira] Created: (FELIX-1324) Add support for runtime debug/launch of felix via eclipse

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.


[jira] Commented: (FELIX-1324) Add support for runtime debug/launch of felix via eclipse

Posted by "Richard S. Hall (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/FELIX-1324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12730408#action_12730408 ] 

Richard S. Hall commented on FELIX-1324:
----------------------------------------

Well, it seems the factory for the launch configuration can now use the standard launching and embedding API to be reasonably generic for most frameworks. I am not sure what else is needed, but it seems like using standard API is the way to go if possible.

> 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.


[jira] Commented: (FELIX-1324) Add support for runtime debug/launch of felix via eclipse

Posted by "David Savage (JIRA)" <ji...@apache.org>.
    [ 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.


[jira] Updated: (FELIX-1324) Add support for runtime debug/launch of felix via eclipse

Posted by "David Savage (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/FELIX-1324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David Savage updated FELIX-1324:
--------------------------------

    Fix Version/s: sigil-1.0.0

> 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
>            Assignee: David Savage
>             Fix For: sigil-1.0.0
>
>
> 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.


[jira] Assigned: (FELIX-1324) Add support for runtime debug/launch of felix via eclipse

Posted by "David Savage (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/FELIX-1324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David Savage reassigned FELIX-1324:
-----------------------------------

    Assignee: David Savage

> 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
>            Assignee: 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.


[jira] Issue Comment Edited: (FELIX-1324) Add support for runtime debug/launch of felix via eclipse

Posted by "David Savage (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/FELIX-1324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12730403#action_12730403 ] 

David Savage edited comment on FELIX-1324 at 7/13/09 10:08 AM:
---------------------------------------------------------------

Not so much, it's more about being able to launch and debug OSGi applications 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.

      was (Author: davemssavage):
    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.


[jira] Updated: (FELIX-1324) Add support for runtime debug/launch of felix via eclipse

Posted by "David Savage (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/FELIX-1324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David Savage updated FELIX-1324:
--------------------------------

    Fix Version/s:     (was: sigil-1.0.0)

move to unscheduled for time being to aid release planning

> 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
>            Assignee: 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.


[jira] Work started: (FELIX-1324) Add support for runtime debug/launch of felix via eclipse

Posted by "David Savage (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/FELIX-1324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Work on FELIX-1324 started by David Savage.

> 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
>            Assignee: 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.


[jira] Commented: (FELIX-1324) Add support for runtime debug/launch of felix via eclipse

Posted by "Richard S. Hall (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/FELIX-1324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12730361#action_12730361 ] 

Richard S. Hall commented on FELIX-1324:
----------------------------------------

What does this mean exactly? Is this something the standard launching and embedding API helps or is it something else?

> 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.