commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "William Pietri (JIRA)" <>
Subject [jira] Commented: (VFS-270) Don't log VFS internal info unless vital
Date Mon, 27 Jul 2009 22:08:14 GMT


William Pietri commented on VFS-270:

Hi, Ralph. I'm not sure if you're talking about my proposed improvement or the temporary workaround
I gave in the comment.

If the former, I'd say no; the easiest thing would be for VFS to default to being quiet unless
there's a problem that an end user would actually care about. I'm currently not using a logging
framework at all for my command-line app.

As to the latter, there could well be easier workarounds. I was just tired of getting a cron
mail every hour, so I rummaged in the debugger to see what objects were involved in producing
the output, and then poked at them until they stopped being noisy. If you have other workarounds,
I'm sure people finding this page via Google would appreciate a cut-and-paste example.

> Don't log VFS internal info unless vital
> ----------------------------------------
>                 Key: VFS-270
>                 URL:
>             Project: Commons VFS
>          Issue Type: Improvement
>    Affects Versions: 1.0
>         Environment: Occurs for me under JDK 1.6 with 32 bit Linux, but presume everywhere.
>            Reporter: William Pietri
>            Priority: Minor
> Please change VFS's default behavior so that it by default no longer produces programmer-focused
info to stdout.
> My situation is that I'm building a command-line tool. I'm using VFS because a) the Java
file API is somewhat awkward, and b) I wanted to have my tool run in a dry-run mode, where
it uses an in-RAM filesystem that gets discarded.
> Even when operating purely on local files, my command-line script produces this output:
> Jul 27, 2009 1:00:02 PM org.apache.commons.vfs.VfsLog info
> INFO: Using "/tmp/vfs_cache" as temporary files store.
> Surely, that's interesting to VFS developers. And maybe that's interesting to me as a
developer using the library, although it makes me wonder why it's creating temporary files
while doing local file access. But that's definitely not interesting to the users of my tool,
especially ones who put it in a cron job, getting regular mail that contains only this.
> My suggestion is twofold:
> 1) Change the default logging levels so that they're tuned to the interests of a typical
app consumer, rather than a developer. This message, for example, should be at DEBUG level
rather than INFO level. 
> 2) Optionally, allow developers who'd like more verbose logging of VFS internals an easy
way to say so. 

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message