logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gary Gregory (JIRA)" <j...@apache.org>
Subject [jira] [Reopened] (LOG4J2-1065) Define org.apache.logging.log4j.Marker.equals(Object) and org.apache.logging.log4j.Marker.hashCode()
Date Sat, 08 Aug 2015 04:28:45 GMT

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

Gary Gregory reopened LOG4J2-1065:
----------------------------------

Reopen to set fix version.

> 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


Mime
View raw message