Teammates: Unstable eclipse behaviour after new merges

[HirdayGupta]

Apologies for a continuous stream of eclipse issues.

After a lot of issues with Eclipse development (Mars 4.5.0), I removed the repo from my computer, redownloaded it, merged from TEAMMATES/master to my repo's master and set up the environment following each step in the documentation, thus peforming a clean install of the new dev environment.

I was able to work successfully & error free for a few hours on a new branch from my now updated master. However, now, once again, Eclipse is absolutely littered with errors (screenshot below). I made absolutely no changes to any settings, and did not even change the branch I was working on. I simply returned to my computer after a while to find this.

Anything at all that could cause something like this? Or will I have to perform another clean install?

[HirdayGupta]

UPDATE: I ran ./gradlew resetEclipseDeps followed by ./gradlew setUpEclipse(again after having already run this during set up) followed by changing the compiler compliance level back to 1.8 and then back again to 1.7, which seems to have fixed the issue for now.

@whipermr5 do you reckon this is a local eclipse problem that keep breaking my project? or something to do with c74ff60?

[wkurniawan07]

@HirdayGupta

./gradlew setupEclipse would already have performed the reset of dependency, thus you should not need to run these two in the first place. The compiler compliance level at 1.7 seems to be a necessary step that I missed during that commit c74ff60; I apologize for that, but it should be fixed in #7123.

Next time something breaks again (I hope it won't, but just in case), do not post the screenshot of the project explorer as it does not tell anything; post the screenshot/contents of the "Markers" tab instead.

[HirdayGupta]

@wkurniawan07 Thanks!

Next time something breaks again (I hope it won't, but just in case), do not post the screenshot of the project explorer as it does not tell anything; post the screenshot/contents of the "Markers" tab instead.

I'll make a note of that.

Also, my compiler compliance was already at 1.7 when it broke. I just set it back to 1.8, cleaned the project (breaking it further) and then set it back to 1.7 and again cleaned the project (which magically fixed it).

[whipermr5]

I just experienced the same issue - very weird indeed. For me, JDK compliance level as well as all GAE settings were reset, as if I'd never set them up at all.

[wkurniawan07]

@whipermr5 that is perhaps because you updated the release branch; essentially deleting the Eclipse settings file again.
I never expect c74ff60 to cause this much trouble, apologies for this 😓

[wkurniawan07]

Closing due to inactivity; seems like all is well. (I hope)