[
https://issues.apache.org/jira/browse/JXR-158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte updated JXR-158:
-------------------------------
Description:
Edit: original title was: StringEntry should implement equals and hashcode
Because it implements Comparable. Per Oracle,
bq. It is strongly recommended, but _not_ strictly required that
{{(x.compareTo(y)==0) == (x.equals(y))}}. Generally speaking, any class that
implements the {{Comparable}} interface and violates this condition should
clearly indicate this fact. The recommended language is "Note: this class has a
natural ordering that is inconsistent with equals."
was:
Edit: changed title from
Because it implements Comparable. Per Oracle,
It is strongly recommended, but _not_ strictly required that
{{(x.compareTo(y)==0) == (x.equals(y))}}. Generally speaking, any class that
implements the {{Comparable}} interface and violates this condition should
clearly indicate this fact. The recommended language is "Note: this class has a
natural ordering that is inconsistent with equals."
> StringEntry shouldn't be Comparable
> -----------------------------------
>
> Key: JXR-158
> URL: https://issues.apache.org/jira/browse/JXR-158
> Project: Maven JXR
> Issue Type: Bug
> Reporter: Elliotte Rusty Harold
> Priority: Minor
>
> Edit: original title was: StringEntry should implement equals and hashcode
> Because it implements Comparable. Per Oracle,
> bq. It is strongly recommended, but _not_ strictly required that
> {{(x.compareTo(y)==0) == (x.equals(y))}}. Generally speaking, any class that
> implements the {{Comparable}} interface and violates this condition should
> clearly indicate this fact. The recommended language is "Note: this class has
> a natural ordering that is inconsistent with equals."
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
