Task #13289 (new)
Opened 8 years ago
Last modified 8 years ago
RFE: review tiffcomment upgrade check warning
| Reported by: | mtbcarroll | Owned by: | dgault |
|---|---|---|---|
| Priority: | minor | Milestone: | n.a. |
| Component: | Bio-Formats | Version: | n.a. |
| Keywords: | n.a. | Cc: | bf@… |
| Resources: | n.a. | Referenced By: | n.a. |
| References: | n.a. | Remaining Time: | n.a. |
| Sprint: | n.a. |
Description (last modified by mtbcarroll)
The upgrade check makes tiffcomment unusable: it dumps the "A new stable version is available" to standard output along with the XML document which is thus now invalid and the command-line help (which I appear to access by not trying a -h or --help option) doesn't give any hint how to suppress it.
Change History (3)
comment:1 Changed 8 years ago by mtbcarroll
- Description modified (diff)
comment:2 Changed 8 years ago by mtbcarroll
comment:3 Changed 8 years ago by rleigh
I was going to file a similar ticket. I noticed this when doing the release testing with older versions.
That upgrade check message should never go to stdout. If it goes to stderr, then stdout can be safely used and redirected without the data being corrupted.
It's also concerning from a usability point of view. If I write a tool which is working just fine, it might end up breaking one day when we make a new release and all my work ends up getting trashed. This could be using the command-line tools in scripts, or it could be using Java code from a script. Whatever the scenario, I think we should firstly ensure it goes to stderr, and secondly rethink the idea of what is essentially "spamming" the user with this stuff.
tail -n +4 appears to be the magic charm.