You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@commons.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2018/09/04 09:10:00 UTC

[jira] [Commented] (LANG-1417) Deprecate ThreadPredicate and ThreadGroupPredicate in favor of java.util.function.Predicate

    [ https://issues.apache.org/jira/browse/LANG-1417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16602795#comment-16602795 ] 

ASF GitHub Bot commented on LANG-1417:
--------------------------------------

Github user britter commented on the issue:

    https://github.com/apache/commons-lang/pull/349
  
    We agreed to just add `@FunctionalInterface` to `ThreadPredicate` and `ThreadGroupPredicate`


> Deprecate ThreadPredicate and ThreadGroupPredicate in favor of java.util.function.Predicate
> -------------------------------------------------------------------------------------------
>
>                 Key: LANG-1417
>                 URL: https://issues.apache.org/jira/browse/LANG-1417
>             Project: Commons Lang
>          Issue Type: Improvement
>          Components: lang.*
>            Reporter: Benedikt Ritter
>            Priority: Major
>             Fix For: 3.9
>
>
> Since we upgraded the Java language requirement to Java 8, we can deprecate our custom ThreadPredicate and ThreadGroupPredicate implementations.
> It looks like our initial plan to let ThreadPredicate and ThreadGroupPredicate extend java.util.function.Predicate is not possible. This is because auf AlwaysTruePredicate and NamePredicate extending both interfaces. This leads to the situation that these classes would inherit from both Predicate<Thread> and Predicate<ThreadGroup>, which is not possible.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)