Community
Participate
Working Groups
This is a very strange error because it is not always reproduceable. I defined an interface with a parameterized return type: -------------------------- package parser; public interface ValueParser<T> { T parse(final String string); } -------------------------- However the return type seems to be not visible for some of the implementations. The strange thing about this behavior is that a "clean project" may clean the error until next compile, sometimes the error did not occur in the different implementation. I tried to create a minimal persion project which could be attached in bugzilla but it doesn't seem to show the bug. The error was shown in line 21 of "test/BooleanParserTest.java".
Created attachment 17837 [details] Minimal project to test. Maybe this test project is too small. My original project had multiple implementations of "ValueParser<T>" but only one at a time showed the strange behavior.
I cannot reproduce with 3.1 M5 candidate (I20040215-2300). Please have a try with M5 when available (end of current week) and reopen if necessary, thanks
I will test the new release. However this error doesn't occur *every* time. If I change something within the file it may work, but if I make a "Clean project" the error reappears. I guess that it might have something to do with internal representation of the parameterized return type or the compiler itself. More feedback after testing.
I've played a while with your project, modified code, rebuilt (incremental and full) and never got the error. If you get it again with M5 please try to provide us a scenario as precise as possible to help us to reproduce it. TIA
I tried the 3.1M5a build but it still happens. I can reproduce it by cleaning all projects while it disappears if I modify the source file and save it. Even if the modification was only a whitespace and reverted before saving. I tried to make a minimal project but it isn't reproduceable on a smaller scale. I could send it to in private if you would like (it consists out of 3 (small) projects, about 234k total already including junit and commons-logging).
Of course, please send it to my internet address: frederic_fusier@fr.ibm.com, thx
*** Bug 85930 has been marked as a duplicate of this bug. ***
Reproduced. It seems that builder does not see dependence to Boolean in BooleanParserTest and compiles it with an UnresolvedReferenceBinding... Kent, I'll forward you Victor's mail with project to reproduce the issue...
Added GenericType test532
Verified in I20050330-0500
