[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=15148867#comment-15148867 ] 

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

The current plan is :

# install a custom servlet which inspects the bundles in the Sling instance for a file named 'pom.properties' located under '/META-INF/maven' and prints the GAV entries as JSON
# Enhance the {{OsgiClient}} to retrieve the list of Maven artifacts deployed in a Sling instance
# In the {{JVMDebuggerConnection}} retrieve the list of Maven Artifacts
# For each artifact trigger a download of the -sources jar
# add each downloaded sources jar as an ExternalArchiveSourceContainer

I have this prototyped in a local checkout, but I still need to figure out step 4.

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