STR: * Make a change in Eclipse that breaks the build (e.g., adding an Exception subclass with no serial UID, which doesn't bother Eclipse but sure bothers our Make process). * Build with mach. (Possibly you need to have Eclipse quit at this point.) * Observe that Eclipse now has no source (e.g., Cmd-Shift-T won't take you to any classes), a broken build, and is spewing errors. * Regenerating the project file doesn't help. Workaround: * Fix the build errors. * Rebuild with mach. * Regenerate project file. * Refresh and rebuild in Eclipse.

(In reply to Richard Newman [:rnewman] from comment #0) > STR: So much good stuff here. > * Make a change in Eclipse that breaks the build (e.g., adding an Exception > subclass with no serial UID, which doesn't bother Eclipse but sure bothers > our Make process). Would be nice to make Eclipse match the build system, wouldn't it? Wonder how hard it is to turn -Xlint args into Eclipse configuration. > * Build with mach. (Possibly you need to have Eclipse quit at this point.) For the record, you can always build with mach. You might interfere with Eclipse's build, and your mach build might need updated moz.build files, but the Eclipse outputs shouldn't interfere with mach at all. > * Observe that Eclipse now has no source (e.g., Cmd-Shift-T won't take you > to any classes), a broken build, and is spewing errors. This surprises me. Will investigate. > * Regenerating the project file doesn't help. This surprises me too. I guess we get to a point where the inner mach build commands spawned by Eclipse start failing, and things go pear-shaped. I would expect that you'd regenerate the project file, refresh and clean, and find that Eclipse is back to normal, but evidently not.

I'm going to close this, since the Eclipse plugin landed in Bug 1029232 surfaces these errors consistently.