Sharing .settings/org.eclipse.buildship.core.prefs between vscode and Eclipse

I am working on a project that is developed by both vscode and Eclipse (different developers). .settings/org.eclipse.buildship.core.prefs is checked into git from Eclipse, and then when the project is opened from vscode, this file is modified (in an unpleasant way - adding a machine-specific java.home and init-script, and changing other settings). This can't be checked in, because it then breaks when opening elsewhere, where the paths are different. It also permutes the .classpath file and other settings files.

java.import.generatesMetadataFilesAtProjectRoot = false is not useful, because the plugin will use the project files if they are present.

The only workaround I can think if is to just remove these from git (ie add to .gitignore). What I would really like is the ability to locate these files in a different location, for Visual Studio (or in a machine configurable way). Then we could keep Eclipse and vscode completely separate.

Is there any other workaround, or possibility of an enhancement to change the file locations?

Iniziare esaminando come l’estensione gestisce .settings/org.eclipse.buildship.core.prefs, .classpath e le altre impostazioni del progetto, inclusa l’impostazione java.import.generatesMetadataFilesAtProjectRoot. Determinare se le posizioni dei metadati del progetto sono configurabili e identificare il comportamento interessato in VS Code ed Eclipse. L’attività è completata quando i due strumenti possono mantenere separati i propri file di progetto senza che vengano sottoposti a commit percorsi specifici della macchina.