Why does not Boolean implement Comparable? (at least in JDK 1.4)

Question

OK, I have read JDK 1.5.0 Beta 2 docs and learned that now java.lang.Boolean implements Comparable<Boolean>.
But why it was not noticed until 1.5?
I can guess that Boolean is not as used as another wrapper classes, and implementing the Comparable interface was not heavily demanded (for instance, requiring a JSR or 500 votes in the Bug Database).
But even Google's Joshua Bloch could have noticed it before...

Answer 1

Additional info from the API v1.4.2:
public interface Comparable
It is strongly recommended (though not required) that natural orderings be consistent with
equals. This is so because sorted sets (and sorted maps) without explicit comparators
behave "strangely" when they are used with elements (or keys) whose natural ordering is
inconsistent with equals. In particular, such a sorted set (or sorted map) violates the gen-
eral contract for set (or map), which is defined in terms of the equals method.
For example, if one adds two keys a and b such that
(!a.equals((Object)b) && a.compareTo((Object)b) == 0)
to a sorted set that does not use an explicit comparator, the second add operation returns
false (and the size of the sorted set does not increase) because a and b are equivalent from
the sorted set's perspective.
Boolean equals
  public boolean equals(Object obj)
Returns true if and only if the argument is not null and is a Boolean object that represents
the same boolean value as this object.
Boolean hashCode
  public int hashCode()
Returns a hash code for this Boolean object.
Overrides: hashCode in class Object
Returns: the integer 1231 if this object represents true; returns the integer 1237 if this
object represents false.Unless I'm missunderstanding something ... If you were to have it implerment Comparable, you coud have two elements in a Set, one true and one false, with true always 1st and false always 2nd. No? If so, what's the point?
~Bill