[
https://issues.apache.org/jira/browse/VFS-270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12735836#action_12735836
]
William Pietri commented on VFS-270:
------------------------------------
Ok. It's your library, so you should feel free to do whatever you want with it.
I'm just trying to make and explain a request. I'm not really interested in
convincing you to do or not do anything.
>From what you say, I gather that one of two (or possibly two of two)
>statements are true.
One: the VFS project participants feel that it's correct behavior that just
using VFS in its default configuration to read and write local files should
result in printing to stdout.
Two: anybody using VFS should be obliged to first get and configure a logging
framework.
>From my perspective, the first is definitely not something I like. I come out
>of the Unix tradition, where tools generally are silent unless there's a major
>problem or output has been explicitly requested.
The second seems like an unnecessary burden to me; when I write library code, I
try to minimize the number of hoops a library user has to jump through. For me
as a VFS user, adding a logging framework just to hush VFS up is a step with a
clear cost and no apparent benefit. And that's once I find out that getting and
configuring a logging framework is a required action; that step definitely took
me more time than the VFS library has so far saved me.
But as I said, it's your project, so as long as you understand why I'm
requesting and why I think it's good, I'm content to be done with this
interaction.
> Don't log VFS internal info unless vital
> ----------------------------------------
>
> Key: VFS-270
> URL: https://issues.apache.org/jira/browse/VFS-270
> 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.
