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 2018/02/26 21:07:02 UTC

[jira] [Updated] (SLING-3759) Support viewing/tailing logs for a defined Sling server

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

Robert Munteanu updated SLING-3759:
-----------------------------------
    Fix Version/s:     (was: Sling Eclipse IDE 1.2.2)
                   Sling Eclipse IDE 1.2.4

> Support viewing/tailing logs for a defined Sling server
> -------------------------------------------------------
>
>                 Key: SLING-3759
>                 URL: https://issues.apache.org/jira/browse/SLING-3759
>             Project: Sling
>          Issue Type: New Feature
>          Components: IDE
>    Affects Versions: Sling Eclipse IDE 1.0.0
>            Reporter: Robert Munteanu
>            Priority: Major
>             Fix For: Sling Eclipse IDE 1.2.4
>
>
> It would be very useful to be able to directly inspect / tail the logs of the Sling runtime instance from a dedicated Eclipse view.
> We should be able to infer the location if we know that the instance is local, but that probably requires a bit of infrastructure work to be able to distinguish local/remote instances.
> For an example involving AEM and a dedicated plugin, see http://labs.sixdimensions.com/blog/2014-07-07/tailing-aem-logs-in-eclipse/



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)