[jira] [Commented] (SLING-3605) Debug based on bundles deployed on the server

["Robert Munteanu (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/SLING-3605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15175901#comment-15175901 ] 

Robert Munteanu commented on SLING-3605:
----------------------------------------

- [r1733325|https://svn.apache.org/r1733325] - print names of source reference being resolved
- [r1733326|https://svn.apache.org/r1733326] - print names of source reference being resolved
- [r1733327|https://svn.apache.org/r1733327] - install the support bundles when connecting in debug mode
- [r1733328|https://svn.apache.org/r1733328] - make source resolution optional
- [r1733329|https://svn.apache.org/r1733329] - rearrange the editor page to make it more balanced

> Debug based on bundles deployed on the server
> ---------------------------------------------
>
>                 Key: SLING-3605
>                 URL: https://issues.apache.org/jira/browse/SLING-3605
>             Project: Sling
>          Issue Type: New Feature
>          Components: IDE
>            Reporter: Robert Munteanu
>            Assignee: Robert Munteanu
>            Priority: Minor
>             Fix For: Sling Eclipse IDE 1.1.0
>
>
> During an offline discussion with [~mpetria] the following item came up: when debugging a Sling application with a large number of bundles, it's hard to synchronise sources between the workspace and the server. It would be good to be able to debug the application based on the information that we have about the running bundles ( e.g. if they are Maven artifacts we can retrieve the sources and associated them to the project ).
> Not trivial but worth looking into.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)