From 814901bfce7828101a758f23681c7043d4c59053 Mon Sep 17 00:00:00 2001 From: Michael Keppler Date: Thu, 26 May 2022 23:17:44 +0200 Subject: Avoid warning "no explicit project encoding" Eclipse 2022-06 raises that warning for each project without explicit encoding. We can avoid the warning by adding explicit project settings for the otherwise implicit encoding. There is no functional change, neither for users of Eclipse nor for users of other IDEs or build tools. Signed-off-by: Michael Keppler Change-Id: I30a6f1369ef09bd445f5730628d01772db2ee7b3 --- org.eclipse.jgit.packaging/.settings/org.eclipse.core.resources.prefs | 2 ++ 1 file changed, 2 insertions(+) create mode 100644 org.eclipse.jgit.packaging/.settings/org.eclipse.core.resources.prefs (limited to 'org.eclipse.jgit.packaging/.settings') diff --git a/org.eclipse.jgit.packaging/.settings/org.eclipse.core.resources.prefs b/org.eclipse.jgit.packaging/.settings/org.eclipse.core.resources.prefs new file mode 100644 index 0000000000..99f26c0203 --- /dev/null +++ b/org.eclipse.jgit.packaging/.settings/org.eclipse.core.resources.prefs @@ -0,0 +1,2 @@ +eclipse.preferences.version=1 +encoding/=UTF-8 -- cgit v1.2.3