Community
Participate
Working Groups
I hate posting non-quite-reproduceable errors, but I have no choice. The (valid) construct below causes this "Problem": *** Bound mismatch: The type DoubleObservation is not a valid substitute for the bounded parameter <T extends TimeSeriesBase.Observable> of the type TimeSeriesBase<T>.Observable<T> DoubleObservation.java *** Now, the funny thing is, if I isolate the snippet (like below), the error does not appear. Furthermore, the first time I played around with copying and pasting the construct to report this bug, the error disappeared from the "Problems" view, only to reappear some days later, after some project changing and "refreshing"... FWIT, here is the construct, closest to the real defs as virtually possible -- two classes are needed: public class TimeSeriesBase { public static interface Observable<T extends Observable> { } } public class DoubleObservation implements TimeSeriesBase.Observable<DoubleObservation> { } Here's the problem view entry: Severity Description Resource Path Location Creation Time Id Project Type Sub Category Bound mismatch: The type DoubleObservation is not a valid substitute for the bounded parameter <T extends TimeSeriesBase.Observable> of the type TimeSeriesBase<T>.Observable<T> DoubleObservation.java zorzella-3awfe/java/com/myproject line 25 March 9, 2006 10:22:29 PM 1064091 zorzella-3awfe Java Problem Let me re-emphasize, this, by itself, on a project, does not reproduce the error...
Which build ID are you using ? Also would this be something occuring when incrementally building only (as opposed to clean build) ?
It's 3.2M3 (I have another bug filed which prevents me from using M4 and above). As for a clean build, I can't say for sure (the project is so large it's hard to experiment -- but I'll see what I can do). But I suspect a clean build would clean the error (because of what I described -- I tried to isolate and reproduce it and the problem disappeared altogether until some later refresh).
Please try to reproduce in latest, and reopen if problems still occur. There were many bug fixes in this area since 3.2M3, and hopefully this should be resolved.
As of now 'LATER' and 'REMIND' resolutions are no longer supported. Please reopen this bug if it is still valid for you.