commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sebb (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (VALIDATOR-349) TLD tables should be pre-sorted
Date Sun, 04 Jan 2015 22:09:34 GMT

     [ https://issues.apache.org/jira/browse/VALIDATOR-349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Sebb resolved VALIDATOR-349.
----------------------------
       Resolution: Fixed
    Fix Version/s: 1.4.1

URL: http://svn.apache.org/r1649436
Log:
VALIDATOR-349 - TLD tables should be pre-sorted

Modified:
    commons/proper/validator/trunk/RELEASE-NOTES.txt
    commons/proper/validator/trunk/src/changes/changes.xml
    commons/proper/validator/trunk/src/main/java/org/apache/commons/validator/routines/DomainValidator.java


> TLD tables should be pre-sorted
> -------------------------------
>
>                 Key: VALIDATOR-349
>                 URL: https://issues.apache.org/jira/browse/VALIDATOR-349
>             Project: Commons Validator
>          Issue Type: Improvement
>            Reporter: Sebb
>             Fix For: 1.4.1
>
>
> The TLD tables are currently sorted at run-time when the class is loaded.
> It would be better to sort the entries in the source table, and have a unit test to check
that they are sorted. The unit test could output the entries in the correct format if it finds
they are not sorted, ready to copy and paste into the source.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message