Community
Participate
Working Groups
I've noticed this incorrect behavior while looking at bug 43270. Note that if this wrong return was fixed then it could be considered as the right implementation of scenario described in related bug 43270. Then, we would get following Error Dialog: "The classfile is not on the classpath" which is the normal behavior as source folder is considered to be in the classpath only for .java files
See also bug 44535
First it was bug 42370 and not 43270! Second, in fact this was intentional as some users complain that class file cannot be opened in source folder. Although it's theoretically true that this folder is not in the classpath, it's diffuclt to explain why we cannot open class files when source files are just in the same folder!