[
https://issues.apache.org/jira/browse/JCR-1695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12677805#action_12677805
]
Michael Dürig commented on JCR-1695:
------------------------------------
AFAIR the 1.5. dependency is not a problem as it occurs in a place which would
be an implementation of a spi logger in the approach I suggested above. We
could just enable/disable building of this particular implementation depending
on the build environment.
> Improve and promote spi-logger
> ------------------------------
>
> Key: JCR-1695
> URL: https://issues.apache.org/jira/browse/JCR-1695
> Project: Jackrabbit Content Repository
> Issue Type: Improvement
> Components: sandbox
> Reporter: Michael Dürig
> Priority: Minor
>
> The spi-logger is very useful for debugging an SPI implementation. However it
> only supports the RepositoryService interface. Other SPI interfaces are not
> supported. Also writing log information as string seems a bit restrictive to
> me. Finally it is not included in the jackrabbit-spi package which introduces
> an additional dependency for debugging.
> I therefore suggest:
> - Add support for the other major SPI interfaces
> - Replace the current way of logging a String to a Writer instance by a more
> versatile mechanism (i.e. clients have to provide an interface which consumes
> more structured log data).
> - Provide some default implementation for the above mechanism (i.e. writing
> to a file, writing to a slf4j based logger, writing to the console...)
> - Promote this project to jackrabbit-spi
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
