Multiproject import fails if subproject eclipse metadata not present

buildship

(Steve Cohen) #1

I am trying to design a multiproject so that none of the eclipse metadata is stored in source control, with the hope that imports would be clean and consistent. This does not appear to be the case. If I delete a subproject’s .settings/org.eclipse.buildship.core.prefs file prior to import, the import fails.

Since this would presumably be metadata that buildship would create on the import process, it should be able to handle the non-existence of this file smoothly.

This is occurring with Buildship 1.0.15.


Coexist with Maven? Looking for a strategy
(Stefan Oehme) #2

If you also remove the .project file it will work. I already have a more graceful handling of broken projects on my list. But since that only happens when someone deliberately deletes half the metadata, it’s not very high priority :wink:


(Steve Cohen) #3

I will look more closely into what’s happening here and get back to you, but my use case was based on a .gitignore that removed ALL the eclipse metadata files from source control, and then reimporting after a fresh pull from the repository. If I’m not wrong about that, then I was removing the .project file.