Mailing-List: contact issues-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: issues@commons.apache.org
Date: Tue, 13 Jan 2015 20:02:42 +0000 (UTC)
From: "Benedikt Ritter (JIRA)" <jira@apache.org>
To: issues@commons.apache.org
Message-ID: <JIRA.12764397.1420043349000.73972.1421179362062@Atlassian.JIRA>
In-Reply-To: <JIRA.12764397.1420043349000@Atlassian.JIRA>
References: <JIRA.12764397.1420043349000@Atlassian.JIRA>
 <JIRA.12764397.1420043349010@arcas>
Subject: [jira] [Closed] (VALIDATOR-349) TLD tables should be pre-sorted
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Benedikt Ritter closed VALIDATOR-349.
-------------------------------------

> 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 Release
>
>
> 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)