diff --git a/JAVA b/JAVA
new file mode 100644
index 000000000..38ec19317
--- /dev/null
+++ b/JAVA
@@ -0,0 +1,30 @@
+import java.util.*;
+
+class p3{
+    Run|Debug
+    public statics  void main(string[] arg) {
+        String s1,s2;
+        Scanner sc = new Snner(sytem.in);
+        s1 = sc.nextline()
+        s2 = sc.nextline()
+        if(s1.length()!=s2.length())
+        {
+        system.out.printin("Not Anagram");
+        return;
+        }
+        char arr1[] = s1.tocharArray();
+        char arr2[] = s2.tocharArray();
+    
+        Arrays.sort(arr1);
+        Arrays.sort(arr2);
+    
+        s1 = new String(arr1);
+        s2 = new String(arr2);
+   
+        if(s1.equals(s2)){
+        system.out.printin("Anagram");
+        else
+        system.out.printin("Not Anagram");
+    
+   }  
+ }   
diff --git a/README.md b/README.md
deleted file mode 100644
index 4bf15f675..000000000
--- a/README.md
+++ /dev/null
@@ -1,70 +0,0 @@
-# Java Debug Server for Visual Studio Code
-
-## Overview
-
-The Java Debug Server is an implementation of Visual Studio Code (VSCode) Debug Protocol. It can be used in Visual Studio Code to debug Java programs.
-
-## Features
-- Launch/Attach
-- Breakpoints
-- Exceptions
-- Pause & Continue
-- Step In/Out/Over
-- Variables
-- Callstacks
-- Threads
-- Debug console
-
-## Background
-
-The Java Debug Server is the bridge between VSCode and JVM. The implementation is based on JDI ([Java Debug Interface](https://docs.oracle.com/javase/7/docs/jdk/api/jpda/jdi/)). It works with [Eclipse JDT Language Server](https://github.com/vscjavaci/eclipse.jdt.ls) as an add-on to provide debug functionalities.
-
-## Repository Structure
-
-- com.microsoft.java.debug.core - the core logic of the debug server
-- com.microsoft.java.debug.plugin - wraps the debug server into an Eclipse plugin to work with Eclipse JDT Language Server
-
-## Installation
-
-### Windows:
-```
-mvnw.cmd clean install
-```
-### Linux and macOS:
-```
-./mvnw clean install
-```
-
-
-## Usage with eclipse.jdt.ls
-
-To use `java-debug` as a [jdt.ls](https://github.com/eclipse/eclipse.jdt.ls) plugin, an [LSP client](https://langserver.org/) has to launch [jdt.ls](https://github.com/eclipse/eclipse.jdt.ls) with `initializationOptions` that contain the path to the built `java-debug` jar within a `bundles` array:
-
-
-```
-{
-    "initializationOptions": {
-        "bundles": [
-            "path/to/microsoft/java-debug/com.microsoft.java.debug.plugin/target/com.microsoft.java.debug.plugin-<version>.jar"
-        ]
-    }
-}
-```
-
-Editor extensions like [vscode-java](https://github.com/redhat-developer/vscode-java) take care of this.
-
-
-Once `eclipse.jdt.ls` launched, the client can send a [Command](https://microsoft.github.io/language-server-protocol/specifications/specification-current/#command) to the server to start a debug session:
-
-```
-{
-  "command": "vscode.java.startDebugSession"
-}
-```
-
-The response to this request will contain a port number on which the debug adapter is listening, and to which a client implementing the debug-adapter protocol can connect to.
-
-
-License
--------
-EPL 1.0, See [LICENSE](LICENSE.txt) file.