Description Bernd K. 2018-01-19 06:48:27 EST

when a perfectly well configured project is imported into a new workspace (for example when checking out an existing project from version control and then importing it into eclipse) the settings for the build output parser is reset to its defaults.

It will ignore the existing .settings/language.settings.xml and instead write a new one with default settings for the build output parser (and possibly other settings too) that break my project. After import I first have to close my project and git reset --hard to restore the corrupted config file into a working order.

Steps to reproduce:

* create a simple makefile project (because this is the kind of project the build output parser is most useful), adjust the settings for build output parser to something that deviates from the defaults, for example choose "per project" instead of "per file" and maybe also change the compiler command pattern¹. Make sure it works, then close the project and make a backup copy of that project folder and archive it for future reference.

* import the project into a fresh workspace or under a different name. Look into the build output parser settings or view the diff of .settings/language.settings.xml

Observations:

* build output parser settings have changed back to their defaults
* the diff shows that .settings/language.settings.xml has been modified during import and existing settings have been destroyed.
* the indexer will not index correctly due to changed BOP settings.

Expected result:

* .settings/language.settings.xml is not changed, all configured settings remain intact and the imported project works the same as before.



___________
¹) For example my compiler is called "arm-none-eabi-gcc" instead of just "gcc" and so I have to change the unflexible default pattern all the time and eclipse keeps resetting the settings every time a colleague wants to check out a project from the repository, this is why this bug hurts embedded developers so much.