[
https://issues.apache.org/jira/browse/SLING-2635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13487768#comment-13487768
]
Robert Munteanu commented on SLING-2635:
----------------------------------------
I think that the most important thing is to have a logging framework in place,
no matter how we do it. I have used the m2e wrapper for logback and there are
some problems with it.
- You can't enable debug logging or change the logging level without going to a
plugin location on disk and modifying logback.properties
- The plugin id in the Eclipse error view will always be the m2e.logback plugin
id, not the originating plugin
What I've used with good success is
- The Eclipse ILog object for messages which should be of intereset to the user
and end up in the Error Log view.
- The [Eclipse tracing
facility|http://wiki.eclipse.org/FAQ_How_do_I_use_the_platform_debug_tracing_facility%3F]
for developer-related logs , which can potentially be turned on by the user .
For instance, since Eclipse 4.2 there is a [Tracing Preference
Page|http://download.eclipse.org/eclipse/downloads/drops4/R-4.2-201206081400/news/eclipse-news-part4.html#TracingPage]
which the user can use to activate/deactive tracing for contributing plugins.
As for the non-Eclipse plugins, we should either settle on a well-known logging
framework, such as Logback, or simply perform no logging and allow the consumer
to provide logging around them. This is what jgit does, and it's embeddable by
defintion
- Eclipse
- Netbeans
- Gerrit
Anyway, until we have 5000+ lines of logging infrastructure I think we can
defer the decision :-) and focus on more shiny features.
> [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
