[
https://issues.apache.org/jira/browse/THRIFT-416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bryan Duxbury updated THRIFT-416:
---------------------------------
Attachment: thrift-416-v3.patch
Here's a slightly modified version of the v3 patch. I think that we should
treat all dependency jars the same way, so I deleted the explicit addition of
log4j's jar to the classpath; it is assumed to be found in thrift.extra.cpath
now instead. Also, I removed the "verbose=true" from the javac line to help
keep the noise down.
What do you think of this version?
> java.util.logging eats exceptions without warning
> -------------------------------------------------
>
> Key: THRIFT-416
> URL: https://issues.apache.org/jira/browse/THRIFT-416
> Project: Thrift
> Issue Type: Bug
> Components: Library (Java)
> Reporter: Jonathan Ellis
> Assignee: Jonathan Ellis
> Attachments:
> 0001-allow-exceptions-to-propagate-up-where-feasible.-on.patch,
> 0002-switch-to-log4j.patch, THRIFT-416-2.patch, thrift-416-v3.patch
>
>
> Using java.util.logging has two related problems.
> One is that virtually no java project in the wild uses it. Everyone uses the
> more advanced log4j.
> Two is that unlike log4j, java.util.logging does not warn you when it is
> swallowing errors because it has not been configured.
> So thrift exceptions vanish without a trace which is bad.
> Here is a patch to switch to log4j.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
