Submitted On 21-FEB-2005
cowwoc
Please note that Atlassian JIRA 3.1 depends upon this bugfix. See http://jira.atlassian.com/browse/JRA-5354 for more information.
Submitted On 24-FEB-2005
swamp_ig
This has affected the ability to run some third party libraries. Would it be so onerous to fix it in the next patch release? It's only a one line change to the source at most.
Submitted On 23-MAR-2005
janhoeve1
Yeah, please fix this one
Submitted On 01-APR-2005
craigwblake
You might want to negate the value in your fix, there. ;-)
Submitted On 29-APR-2005
Apoptosis66
This bug effects the Apache Torque framework, and the Quartz Scheduler.
Submitted On 01-MAY-2005
amit_h
Guys this is getting fixed in the current development release of Java which is code named Project Mustang.
But we will need your active support to verify the fix.
Submitted On 02-MAY-2005
Apoptosis66
Correct me if I am wrong but Mustang is java 6.0 (1.6)? I personally think this is not soon enough. I have a team of developers who are fiending to move to Java 1.5 but can't because of third party libraries we rely on. All of which are waiting for this bug to fix. I think it would be a shame to make everyone wait a whole release, for what appears to be a one or two line fix. What is the issue with getting this into 1.5 update 4?
Submitted On 06-JUL-2005
vor23
To avoid the stack overflow in the proposed solution, use this instead:
public int compareTo(java.util.Date d) {
return (d instanceof Timestamp) ? compareTo((Timestamp) d) : d.compareTo(this);
}
Submitted On 13-JUL-2005
Apoptosis66
So maybe 1.5 Update 5 :)
Submitted On 08-SEP-2005
This needs to get fixed in 1.5. This does introduce backwards incompatibility that is only detectable in run-time, not in compile time.
Submitted On 19-SEP-2005
Apoptosis66
So maybe 1.5 Update 6? This is getting nuts. How are major features like changes to LDAP Api going into updates, where as this regression bug, that is a simple fix does not?
Submitted On 06-OCT-2005
obsidian
What's the point of making everyone wait years for this fix? There is clearly no problem doing bugfix releases. This absolutely should be fixed in the next one.
Moving to 1.5 is a big problem for most people today (if not altogether impossible) - __because of bugs like this__.
If you won't fix this in 1.5, you may as well not fix it at all. 1.6 will introduce 100 new showstoppers that you won't fix until 1.7... and the cycle will continue...
Submitted On 11-OCT-2005
smithk10
why is sun holding java developers hostage? going to have to stay on 1.4 and then move to a non-java solution. 13 months since being reported! insane.
Submitted On 26-OCT-2005
matt@slc
How about:
public int compareTo(Date d) {
return (d instanceof Timestamp) ?
compareTo((Timestamp)d) :
-d.compareTo(this);
}
Submitted On 02-MAR-2006
asioanid
please, can you guys at sun give us a statement about the scheduling of jdk5.0u7? we have lots of banking software which cannot be run under 5.0 cuz of this bug :-((
Submitted On 15-MAR-2006
rmcgeary
18 months and this backwards compatibility issue still isn't resolved? Truthfully, this should have been fixed before 1.5 came out of beta. How long until 1.5u7? How sad.
Submitted On 23-APR-2006
wbolivar
What is going on with this bug? We have been waiting for the resolution of this stuff but is still there, you said this bug was included on the jdk5.0u7 on January the 2th but that version dose not exist yet.
Submitted On 14-JUN-2006
nrkonjeti
I think there is a fix in 5.0 release.
Submitted On 14-JUN-2006
nrkonjeti
check 5.0 , it is solved no need to use third party solutions
Submitted On 14-JUN-2006
nrkonjeti
I think there is a fix in 5.0 release.
Submitted On 06-OCT-2006
down
down
PLEASE NOTE: JDK6 is formerly known as Project Mustang
|