[
https://issues.apache.org/jira/browse/IMAGING-154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16352302#comment-16352302
]
Bruno P. Kinoshita commented on IMAGING-154:
--------------------------------------------
Hi Gilles,
I think this was one of the blockers for 1.0. But you are right, there was no
discussion in the mailing list. My guess is that we won't reach consensus
easily.
Initially my preference is always to remove logging/debugging from commons
libraries, unless really necessary or useful. And I will admit that some time
ago when I tried to troubleshoot TIFF issues, the dump/debug features helped
immensely. Said that, I could achieve the same with a bit more of time, and
some help of the Eclipse debugger and a piece of paper and pen.
I'm OK with a solution like Log4J, especially if it provides a good replacement
for the dump methods.
So let me start a discussion in the mailing list to see what others think, and
postpone merging the PR :)
Thanks!
B
> Remove Debug class
> ------------------
>
> Key: IMAGING-154
> URL: https://issues.apache.org/jira/browse/IMAGING-154
> Project: Commons Imaging
> Issue Type: Task
> Affects Versions: Patch Needed
> Reporter: Benedikt Ritter
> Assignee: Bruno P. Kinoshita
> Priority: Major
> Fix For: 1.0
>
>
> Low level libraries should not do logging, but communicate through the use of
> exceptions and meaningful return values. Remove the Debug class and all it's
> uses.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
