[
https://issues.apache.org/jira/browse/PDFBOX-472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12744407#action_12744407
]
Hannes Erven commented on PDFBOX-472:
-------------------------------------
Is there any progress on this issue? Is help needed?
I've run into the same problem (Eclipse RCP app with read-only install area)
and temporarily "fixed" this by changing the log file path to
File.createTempFile() if the "PDFBox.log" is not writeable by the user. My
modification is (LoggingObject.java line 34):
File logFile = new File("PDFBox.log");
if (! (
(logFile.exists() || logFile.createNewFile())
&&
logFile.canWrite()
)
){
logFile = File.createTempFile("PDFBox", ".log");
}
FileHandler fh = new FileHandler(logFile.getCanonicalPath(), true);
> use commons logging
> -------------------
>
> Key: PDFBOX-472
> URL: https://issues.apache.org/jira/browse/PDFBOX-472
> Project: PDFBox
> Issue Type: Improvement
> Affects Versions: 0.8.0-incubator
> Reporter: Sean Bridges
> Fix For: 0.8.0-incubator
>
> Attachments: logpatch
>
>
> LoggingObject logs all pdfbox output to a file PDFBox.log using
> java.util.logging. The app may not have permission to create this file, the
> user probably won't be looking at it for errors, and for long running server
> tasks, this file may grow very large.
> It would be much nicer to simply use apache commons logging (or even SLF4J)
> and allow the application to setup logging as they see fit.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
