[jira] [Commented] (VALIDATOR-403) Accept Discover cards of 17 digits long that start with 6011

[ https://issues.apache.org/jira/browse/VALIDATOR-403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15853402#comment-15853402 ] Sebb commented on VALIDATOR-403: According to

[jira] [Resolved] (VALIDATOR-413) Generic CreditCard validation

[ https://issues.apache.org/jira/browse/VALIDATOR-413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebb resolved VALIDATOR-413. Resolution: Fixed Fix Version/s: 1.5.2 URL: http://svn.apache.org/viewvc?rev=1781815=rev Log:

[jira] [Created] (VALIDATOR-414) Simplify CreditCard validation

Sebb created VALIDATOR-414: -- Summary: Simplify CreditCard validation Key: VALIDATOR-414 URL: https://issues.apache.org/jira/browse/VALIDATOR-414 Project: Commons Validator Issue Type: Improvement

[jira] [Updated] (VALIDATOR-403) Accept Discover cards of 17 digits long that start with 6011

[ https://issues.apache.org/jira/browse/VALIDATOR-403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebb updated VALIDATOR-403: --- Component/s: (was: Framework) CreditCard > Accept Discover cards of 17 digits long

[jira] [Updated] (VALIDATOR-404) Support Maestro, Solo and Switch cards

[ https://issues.apache.org/jira/browse/VALIDATOR-404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebb updated VALIDATOR-404: --- Component/s: CreditCard > Support Maestro, Solo and Switch cards > --

[jira] [Updated] (VALIDATOR-413) Generic CreditCard validation

[ https://issues.apache.org/jira/browse/VALIDATOR-413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebb updated VALIDATOR-413: --- Component/s: CreditCard > Generic CreditCard validation > - > >

[jira] [Updated] (VALIDATOR-408) Please fix DISCOVER Card Validation Patterns

[ https://issues.apache.org/jira/browse/VALIDATOR-408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebb updated VALIDATOR-408: --- Component/s: CreditCard > Please fix DISCOVER Card Validation Patterns >

[jira] [Created] (VALIDATOR-413) Generic CreditCard validation

Sebb created VALIDATOR-413: -- Summary: Generic CreditCard validation Key: VALIDATOR-413 URL: https://issues.apache.org/jira/browse/VALIDATOR-413 Project: Commons Validator Issue Type: Improvement

[jira] [Resolved] (VALIDATOR-236) Optional ranges for xxxRange validations

[ https://issues.apache.org/jira/browse/VALIDATOR-236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebb resolved VALIDATOR-236. Resolution: Won't Fix AFAICT it's not possible. The isInRange() methods take a value which is of the

[jira] [Updated] (VALIDATOR-408) Please fix DISCOVER Card Validation Patterns

[ https://issues.apache.org/jira/browse/VALIDATOR-408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebb updated VALIDATOR-408: --- Fix Version/s: (was: 1.5.2) > Please fix DISCOVER Card Validation Patterns >

[jira] [Resolved] (VALIDATOR-197) Copy remaining Validation Routines to the new routines package

[ https://issues.apache.org/jira/browse/VALIDATOR-197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebb resolved VALIDATOR-197. Resolution: Done Seems to be done > Copy remaining Validation Routines to the new routines package >

[jira] [Resolved] (VALIDATOR-258) EmailValidator: the tld should be checked against some sort of configurable list

[ https://issues.apache.org/jira/browse/VALIDATOR-258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebb resolved VALIDATOR-258. Resolution: Implemented The code checks the domain using the DomainValidator. > EmailValidator: the tld

[jira] [Commented] (VALIDATOR-390) Upgrade to Commons Collections 4.x

[ https://issues.apache.org/jira/browse/VALIDATOR-390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15853335#comment-15853335 ] Sebb commented on VALIDATOR-390: CC 4.x no longer includes FastHashMap. Unfortunately it's not

[jira] [Resolved] (VALIDATOR-397) Allow default values if validation fails

[ https://issues.apache.org/jira/browse/VALIDATOR-397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebb resolved VALIDATOR-397. Resolution: Won't Fix > Allow default values if validation fails >

[jira] [Commented] (VALIDATOR-404) Support Maestro, Solo and Switch cards

[ https://issues.apache.org/jira/browse/VALIDATOR-404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15853331#comment-15853331 ] Sebb commented on VALIDATOR-404: If you just want to validate the checkdigit, you can use a validator

[jira] [Resolved] (VALIDATOR-260) ValidatorAction should handle missing jsFunction nicer

[ https://issues.apache.org/jira/browse/VALIDATOR-260?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebb resolved VALIDATOR-260. Resolution: Won't Fix Javascript validation is no longer supported. See VALIDATOR-371 > ValidatorAction

[jira] [Resolved] (VALIDATOR-270) allow to determine NLS resource by other inputs via call-back method

[ https://issues.apache.org/jira/browse/VALIDATOR-270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebb resolved VALIDATOR-270. Resolution: Invalid Does not appear to relate to Commons Validator > allow to determine NLS resource by

[jira] [Resolved] (VALIDATOR-365) An arbitrarily large email string causes stackoverflowerror in EmailValidator.isValid()

[ https://issues.apache.org/jira/browse/VALIDATOR-365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebb resolved VALIDATOR-365. Resolution: Not A Problem > An arbitrarily large email string causes stackoverflowerror in >

[jira] [Resolved] (VALIDATOR-379) CodeValidator unconditionally trim()s the input string

[ https://issues.apache.org/jira/browse/VALIDATOR-379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebb resolved VALIDATOR-379. Resolution: Fixed Fix Version/s: 1.5.2 Document the behaviour: URL:

[jira] [Resolved] (VALIDATOR-387) Userinfo without colon should be valid in UrlValidator

[ https://issues.apache.org/jira/browse/VALIDATOR-387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebb resolved VALIDATOR-387. Resolution: Fixed Fix Version/s: 1.5.2 URL: http://svn.apache.org/viewvc?rev=1781788=rev Log:

[jira] [Resolved] (VALIDATOR-388) Email Validator accepts invalid E-Mail Address

[ https://issues.apache.org/jira/browse/VALIDATOR-388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebb resolved VALIDATOR-388. Resolution: Invalid I disagree; in this case I think Wikipedia is wrong. RFC 3696 says (page 5): The

[jira] [Resolved] (VALIDATOR-394) General Modulus Ten Check Digit Implementation

[ https://issues.apache.org/jira/browse/VALIDATOR-394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebb resolved VALIDATOR-394. Resolution: Fixed Fix Version/s: 1.5.2 Document addition: URL:

[jira] [Resolved] (VALIDATOR-402) ISIN validator

[ https://issues.apache.org/jira/browse/VALIDATOR-402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebb resolved VALIDATOR-402. Resolution: Implemented Already exists as ISINCheckDigit > ISIN validator > -- > >

[jira] [Commented] (VALIDATOR-408) Please fix DISCOVER Card Validation Patterns

[ https://issues.apache.org/jira/browse/VALIDATOR-408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15853289#comment-15853289 ] Sebb commented on VALIDATOR-408: Discovered the following, which looks official:

[jira] [Resolved] (VALIDATOR-409) API InetAddressValidator.isValidInet6Address() fails to validate IPv6 address.

[ https://issues.apache.org/jira/browse/VALIDATOR-409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebb resolved VALIDATOR-409. Resolution: Cannot Reproduce No feedback; cannot determine if there is a problem, let alone fix it if

[jira] [Commented] (CLI-257) Allow partial parsing

[ https://issues.apache.org/jira/browse/CLI-257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15853250#comment-15853250 ] Benedikt Ritter commented on CLI-257: - Thank you [~johann_petrak]! This looks like a partial fix, which

[GitHub] commons-lang pull request #233: Fix a few broken @literal tags

Github user asfgit closed the pull request at: https://github.com/apache/commons-lang/pull/233 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature

[GitHub] commons-lang issue #233: Fix a few broken @literal tags

Github user PascalSchumacher commented on the issue: https://github.com/apache/commons-lang/pull/233 Thanks! --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes