[jira] [Created] (COLLECTIONS-403) Make AndPredicate, AnyPredicate etc. not final
Make AndPredicate, AnyPredicate etc. not final -- Key: COLLECTIONS-403 URL: https://issues.apache.org/jira/browse/COLLECTIONS-403 Project: Commons Collections Issue Type: Improvement Components: Collection Affects Versions: 3.2.1 Reporter: david cogen Priority: Minor If there is no good reason for these (and similar classes) to not be final, they would be much more useful to me if they were not final. I have a class that I wanted to have an "is a" relation to AnyPredicate, but, AnyPredicate being declared final, I cannot and instead have to design it with a "has a" relation to AnyPredicate, which for my purpose is much less clear. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (LANG-787) StringUtils.RemoveIgnoreCase desired
StringUtils.RemoveIgnoreCase desired Key: LANG-787 URL: https://issues.apache.org/jira/browse/LANG-787 Project: Commons Lang Issue Type: New Feature Components: lang.* Affects Versions: 3.1 Reporter: david cogen Priority: Minor removeStartIgnoreCase() and removeEndIgnoreCase() exist, so why not removeIgnoreCase() Specifically: String removeIgnoreCase(String str, String remove) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (LANG-773) ImmutablePair doc contains nonsense text
ImmutablePair doc contains nonsense text Key: LANG-773 URL: https://issues.apache.org/jira/browse/LANG-773 Project: Commons Lang Issue Type: Bug Components: lang.tuple.* Affects Versions: 3.1 Reporter: david cogen Priority: Minor Description of this class contains the following nonsense text: #ThreadSafe# if the objects are threadsafe -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (LANG-772) ClassUtils.PACKAGE_SEPARATOR javadoc contains garbage text
ClassUtils.PACKAGE_SEPARATOR javadoc contains garbage text -- Key: LANG-772 URL: https://issues.apache.org/jira/browse/LANG-772 Project: Commons Lang Issue Type: Bug Components: lang.* Affects Versions: 3.0.1 Reporter: david cogen Priority: Minor javadoc description of ClassUtils.PACKAGE_SEPARATOR is as follows: The package separator String: ".". It should be something like the following: The package separator String: ".". -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (LANG-769) Please restore NotImplementedException and UnhandledException
Please restore NotImplementedException and UnhandledException - Key: LANG-769 URL: https://issues.apache.org/jira/browse/LANG-769 Project: Commons Lang Issue Type: Improvement Reporter: david cogen Priority: Minor Why were these removed? I found these very useful and used them often. As the version 2.6 api javadoc states, "This exception supplements the standard exception classes by providing a more semantically rich description of the problem." Just want you to realize that these have found direct use outside the library; not just internal use within commons-lang. I will define these missing classes myself, or maybe include both commons-lang and commons-lang3 (but I really don't to do that). It would be very nice to have these back. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
