You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Dan Klco (JIRA)" <ji...@apache.org> on 2012/10/31 13:47:13 UTC
[jira] [Comment Edited] (SLING-2635) [Tooling] Logging framework
for Slingclipse
[ https://issues.apache.org/jira/browse/SLING-2635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13487717#comment-13487717 ]
Dan Klco edited comment on SLING-2635 at 10/31/12 12:46 PM:
------------------------------------------------------------
I think it may be cleaner to abstract the logging. I can look into creating a SLF4J wrapper for the Plugin's Eclipse logger. That way we can swap out with whatever we'd want if we decide to move in a different direction.
was (Author: klcodanr):
I'd actually recommend abstracting the logging. I can look into creating a SLF4J wrapper for the Plugin's Eclipse logger. That way we can swap out with whatever we'd want if we decide to move in a different direction.
> [Tooling] Logging framework for Slingclipse
> -------------------------------------------
>
> Key: SLING-2635
> URL: https://issues.apache.org/jira/browse/SLING-2635
> Project: Sling
> Issue Type: Sub-task
> Components: Extensions
> Reporter: Antonio Sanso
> Assignee: Antonio Sanso
> Attachments: SLING-2635.diff
>
>
> We need a Logging framework for Slingclipse.
> I see two options at the moment:
> - using a log framework as SLF4J logger or other similar
> - using the embedded Eclipse logging framework
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira