## Description This sample extension illustrate how to access workspaces to retrieve configured commands and execute it with a simple action. Read the tutorial at: https://www.eclipse.org/che/docs/plugins/native-access-to-the-workspace/index.html The following sample will create a new file called "che-was-here" in the project by using the native "touch" command. ## How to test sample-plugin-nativeaccess plugin ### 1- Link to IDE Assembly The plugin-nativeaccess extension is only a client-side (IDE) extension. You have to introduce the extension as a dependency in `/che/assembly/assembly-ide-war/pom.xml`. Add: ```XML ... org.eclipse.che.sample che-sample-plugin-nativeaccess-ide ... ``` You can insert the dependency anywhere in the list. After you have inserted it, run `mvn sortpom:sort` and maven will order the `pom.xml` for you. ### 2- Rebuild Eclipse Che ```Shell # Build a new IDE.war # This IDE web app will be bundled into the assembly cd che/assembly/assembly-ide-war mvn clean install # Create a new Che assembly that includes all new server- and client-side extensions cd assembly/assembly-main mvn clean install ``` ### 3- Run Eclipse Che ```Shell # Start Che using the CLI with your new assembly # Replace with the path to your Che repository, to use local binaries in your local image # Replace with the actual version you are working on docker run -it --rm -v /var/run/docker.sock:/var/run/docker.sock \ -v :/data \ -v :/repo \ eclipse/che: start --debug ``` ### Documentation resources - IDE Setup: https://www.eclipse.org/che/docs/plugins/setup-che-workspace/index.html - Building Extensions: https://www.eclipse.org/che/docs/plugins/create-and-build-extensions/index.html - Run local Eclipse Che binaries: https://www.eclipse.org/che/docs/setup/configuration/index.html#development-mode