DO NOT REPLY [Bug 22473] New: - Date selector's behavior is inconsistent with its documentation

[bu...@apache.org]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22473>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=22473

Date selector's behavior is inconsistent with its documentation

           Summary: Date selector's behavior is inconsistent with its
                    documentation
           Product: Ant
           Version: 1.6Alpha (nightly)
          Platform: All
        OS/Version: Other
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Core
        AssignedTo: dev@ant.apache.org
        ReportedBy: gudnabrsam@yahoo.com


The docs say that the default "when" setting of DateSelector is "before".  The 
index of "before" in the DateSelector.TimeComparisons EnumeratedAttribute is 
0.  However, DateSelector's private int cmp member is initialized to 2, the 
index of "equal".  This makes working with DateSelector produce slightly 
unexpected results.  The workaround is not to expect DateSelector to behave 
properly by default, always using the when attribute.  Because I need "after" 
behavior I am not hindered by this bug personally; however I would be inclined 
to think it needs the five seconds of attention either to fix the Java code or 
the documentation to be in accord.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org