You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Robert Munteanu (JIRA)" <ji...@apache.org> on 2016/03/02 16:34:18 UTC

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

     [ https://issues.apache.org/jira/browse/SLING-3605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robert Munteanu reopened SLING-3605:
------------------------------------

Reopening to address some minor usability issues

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