[
https://issues.apache.org/jira/browse/SLING-3759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14060659#comment-14060659
]
Justin Edelson commented on SLING-3759:
---------------------------------------
Actually, it looks like Beagle doesn't work on Kepler or Luna (see
jira.qos.ch/browse/CONSPLUG-44), but perhaps one of our Eclipse plugin experts
can fix that issue :)
> 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
> Fix For: Sling Eclipse IDE 1.1.0
>
>
> 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
(v6.2#6252)
