You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by "Gary Gregory (JIRA)" <ji...@apache.org> on 2015/08/08 06:28:45 UTC
[jira] [Updated] (LOG4J2-1065) Define
org.apache.logging.log4j.Marker.equals(Object) and
org.apache.logging.log4j.Marker.hashCode()
[ https://issues.apache.org/jira/browse/LOG4J2-1065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gary Gregory updated LOG4J2-1065:
---------------------------------
Fix Version/s: 2.4
> Define org.apache.logging.log4j.Marker.equals(Object) and org.apache.logging.log4j.Marker.hashCode()
> ----------------------------------------------------------------------------------------------------
>
> Key: LOG4J2-1065
> URL: https://issues.apache.org/jira/browse/LOG4J2-1065
> Project: Log4j 2
> Issue Type: Improvement
> Components: API
> Affects Versions: 2.3
> Reporter: Gary Gregory
> Fix For: 2.4
>
>
> Define {{org.apache.logging.log4j.Marker.equals(Object)}} and {{org.apache.logging.log4j.Marker.hashCode()}}.
> This does not change compatibility since equals and hashCode are defined in {{java.lang.Object}}.
> Note that the Log4j class {{org.apache.logging.log4j.MarkerManager.Log4jMarker}} already implements these methods, so there is no change in behavior.
> Benefits are:
> - Clearly defined these methods.
> - Code generation tools like Eclipse can avoid issuing warnings when generating code that use equals and hashCode but the only version of these methods it sees are from {{java.lang.Object}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org