From fe355b77bbb54434c91edb5cae2485fcd6aab9cf Mon Sep 17 00:00:00 2001
From: Kirill Likhodedov <Kirill.Likhodedov@jetbrains.com>
Date: Tue, 19 Mar 2019 15:04:47 +0300
Subject: [PATCH] tests: don't allow to define equals & hashCode for the
 MockVirtualFile

Several tests rely on the identity equals for MockVirtualFile, and for now, there is no infrastructure to support equals & hashCode, as it is done for regular VirtualFiles. Therefore it is better to mark explicitly that equals & hashCode shouldn't be defined here.
---
 .../src/com/intellij/mock/MockVirtualFile.java         | 10 ++++++++++
 1 file changed, 10 insertions(+)

diff --git a/platform/testFramework/src/com/intellij/mock/MockVirtualFile.java b/platform/testFramework/src/com/intellij/mock/MockVirtualFile.java
index 96d37ff08796..66d3dffb1bad 100644
--- a/platform/testFramework/src/com/intellij/mock/MockVirtualFile.java
+++ b/platform/testFramework/src/com/intellij/mock/MockVirtualFile.java
@@ -126,6 +126,16 @@ public class MockVirtualFile extends VirtualFile {
     return VfsUtilCore.toVirtualFileArray(myChildren);
   }
 
+  @Override
+  public final boolean equals(Object o) {
+    return super.equals(o);
+  }
+
+  @Override
+  public final int hashCode() {
+    return super.hashCode();
+  }
+
   @NotNull
   @Override
   public OutputStream getOutputStream(Object requestor, long newModificationStamp, long newTimeStamp) throws IOException {