commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Emmanuel Bourg (JIRA)" <>
Subject [jira] Updated: (CLI-170) TypeHandler prints messages to stderr
Date Sun, 09 Nov 2008 21:32:46 GMT


Emmanuel Bourg updated CLI-170:

         Priority: Minor  (was: Major)
    Fix Version/s:     (was: 1.2)
       Issue Type: Improvement  (was: Bug)

> TypeHandler prints messages to stderr
> -------------------------------------
>                 Key: CLI-170
>                 URL:
>             Project: Commons CLI
>          Issue Type: Improvement
>          Components: Validation
>    Affects Versions: 1.2
>            Reporter: J. Lewis Muir
>            Priority: Minor
>             Fix For: 1.3
>         Attachments: remove-messages-to-stderr.patch
>   Original Estimate: 0.5h
>  Remaining Estimate: 0.5h
> Certain methods in {{TypeHandler}} print a message to stderr when they are unable to
create the object they are to return.  I don't think this should be.  The documentation for
each method clearly states that if it is unable to create the object, it returns {{null}}.
 If more information should be reported to the caller, these methods should be changed to
throw an exception.  I've removed the printing of these messages from {{TypeHandler}}.
> This fix also makes the unit test output clean.  Right now, certain test cases exercise
the "returns {{null}}" behavior of some of the {{TypeHandler}} methods, and this causes various
error messages to be written to stderr which makes the test case output look unclean and like
something has gone wrong when in fact everything is working correctly.
> Attached is a patch for this fix.  The patch is against [].

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

View raw message