Community
Participate
Working Groups
Build 20020503: I have a file that compiles clean. There are not compile errors. However I can see the red problem highlight in the editor that shows: "the import cannot be resolved..." I'm confused, because if the import cannot be resolved how did the file compile clean in the first place? This started to occur after someone in our team refactored some classes and moved them to another package. I've caught up with the changes, all plugins compile, but the editor shows these highlight errors all over the place.
the reconciler is currently only run after a change by the user. So what could have happened is that the reconciler was run with the old packages. The error has shown up. Then you did a catch-up with the team and got the correct packages. You did a rebuild and the compiler could build fine. When you add a space to the original document the errors should go away. Could this be your scenario?
It happend to me as well. Here is the scenario: 1) Debug moved some classes into another package 2) Updated from repository 3) Class JUnit tab group had compile errors 4) did an organize import and rebuild -> the temporary problems where still there. 5) modified the file to force a reconcile -> the temporary problems where still there 6) closing and reopening the file - still no luck After closing and reoping the project, building and reopening the temporary problems where gone.
David - can you verify with latest ? Should have been solved for 20020521.
The bug still occur in build 20020528.
add a new PackageFragment does not update the name lookup of dependent projects Fixed.
Verified.
