Community
Participate
Working Groups
I20071030-0010. Enable "Method overridden but not package visible:" i.e. COMPILER_PB_OVERRIDING_PACKAGE_DEFAULT_METHOD (is enabled by default). In case of shadowed static methods I don't see any advantage of getting the following problem reported: The method YYY.bar() does not override the inherited method from XXX since it is private to a different package P/src/foo A static method always shadows the one from the super class even if both are declared as public - in which case no warning is reported. Test Case: --- %< --- package bar; public class XXX { static void foo() { } } --- %< --- package foo; public class YYY extends bar.XXX { static void foo() { // WARNING HERE } }
Any update on this one? This causes a compile warning that gets reported on each Eclipse build. I'd like this list to be as small as possible. See: http://eclipsebuildserv.ottawa.ibm.com/downloads/master/downloads/drops/I20071210-1800/compilelogs/plugins/org.eclipse.ui.presentations.r21_3.2.100.I20071031-0010/@dot.bin.html
As far as I know this has already been addressed by Kent.
>As far as I know this has already been addressed by Kent. You mean he works on this and hasn't committed the code? Observe that the warning is in I20071210-1800.
The Eclipse builds are not using the compiler from the latest build. They use the compiler version from the latest milestone. Kim, does this have been changed ?
Tested with test case from comment 0 using I20071211-0010. This seems to be fixed indeed.
I only update the builder with the plugins from every milestone unless I get a request to do so to address a particular bug fix. So you're asking me to use the latest version of jdt.core in the builder for the next builds toward M4?
It's not critical. I would proceed as usual.
Kent, is there some more work planned on this one? It seems to be fixed in 3.4 M4.
This was fixed a while ago. Added MethodVerifyTest.test160 Released for 3.4M7
Verified for 3.4M7 using I20080427-2000
