org.eclipse.jdt.core.prefs: Why is it checked in?

[Cantor, Scott]

On 11/19/18, 8:59 AM, "dev on behalf of Rod Widdowson" <dev-bounces at shibboleth.net on behalf of rdw at steadingsoftware.com> wrote:

> As of not so very long ago, git is spending a lot of time telling me that "org.eclipse.jdt.core.prefs" (in every folder in 
> every project) is out of date.  This might be because I updated from Java7 just recently, or it might be that my laptop
> is running the latest eclipse (although I get the same error when I plug my work disk into my desktop running eclipse
> "Oxygen (4.7.3a)"

Well, one point is that when you do a Maven Project update, it almost always touches various files like that with whatever its latest settings are. That may be part of it.

> The differences are quite interesting:

I assume those are "master" branches, and that's just reflecting the parent POM change, which changes the Java version. With Eclipse, getting the real time build to match the Maven build does include those settings, though I suppose we could not check it in and just have people import the Maven projects themselves.

But we were also trying to standardize the various Eclipse build settings like warnings, to avoid inconsistency there, and I think that requires checking that file in. And I don't, for example, commit changes to that file when I do local testing with e.g. the null annotation analysis because we haven't agreed to turn that on yet.

-- Scott