From a1f424853bef2c48aab3d044a2b89f8d65285c25 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Jo=C3=A3o=20Dinis=20Ferreira?= Date: Thu, 23 Jul 2026 20:58:28 +0200 Subject: [PATCH] chore(oomph): pin the workspace line delimiter to LF MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The repository stores and checks out LF everywhere (.gitattributes, line-endings CI check, project-scoped line.separator settings), and the generation pipelines emit LF deterministically. The one remaining platform-dependent default is the workspace-level Eclipse preference: on a fresh Windows workspace, "New text file line delimiter" falls back to the platform separator (CRLF), so anything created outside the project-scoped settings — and any Xtext IDE generation resolving the workspace preference — can still churn against the LF checkout. Provision /instance/org.eclipse.core.runtime/line.separator = "\n" in the Oomph product setup so every DDK Eclipse starts with a Unix line delimiter workspace-wide. The value is an XML character reference so attribute normalization preserves the newline. Co-Authored-By: Claude Fable 5 --- ddk-configuration/oomph-setup/DDKEclipse.setup | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/ddk-configuration/oomph-setup/DDKEclipse.setup b/ddk-configuration/oomph-setup/DDKEclipse.setup index 56afe38219..b5b6532783 100644 --- a/ddk-configuration/oomph-setup/DDKEclipse.setup +++ b/ddk-configuration/oomph-setup/DDKEclipse.setup @@ -96,6 +96,10 @@ key="/instance/org.eclipse.core.resources/missingNatureMarkerSeverity"> record + + record + record @@ -129,6 +133,14 @@ key="/instance/org.eclipse.core.resources/missingNatureMarkerSeverity" value="0"/> + + +