Code Server fixed for Windows Users (now shuts down correctly)

[Craig Mitchell]

Thomas fixed the code server for Windows users: https://github.com/tbroyer/gwt-maven-plugin/issues/110#issuecomment-3405235827

Thanks Thomas!

Thought I'd clean up my IntelliJ dev startup.  What I figured out is:

1. Create a maven launcher for the codeserver.
2. Create a maven launcher for your server.
3. And you can create maven launches for thinks like your DB.
4. Then create a compound launcher to start everything with one click.  IntelliJ also gives you a "Stop All" button to stop everything with one click.

Much easier!

To create a maven launcher for your DB, you use "exec-maven-plugin".  For example, I'm using Google App Engine, so I added this to my pom.xml:

<plugin>
  <groupId>org.codehaus.mojo</groupId>
  <artifactId>exec-maven-plugin</artifactId>
  <version>${exec-maven-plugin.version}</version>
  <executions>
    <execution>
      <id>start-datastore-emulator</id>
      <goals>
        <goal>exec</goal>
      </goals>
      <configuration>
        <executable>gcloud</executable>
        <arguments>
           <argument>beta</argument>
            <argument>emulators</argument>
            <argument>datastore</argument>
            <argument>start</argument>
            <argument>--use-firestore-in-datastore-mode</argument>
            <argument>--data-dir=local_db</argument>
          </arguments>
       </configuration>
     </execution>
  </executions>
</plugin>

Now I just create a maven launcher in IntelliJ "exec:exec@start-datastore-emulator" and it'll start my local DB.

If anyone has any tips for improving it, please let me know.

[Craig Mitchell]

Forgot to say, the reason for starting everything via a maven launcher, is so IntelliJ knows it's running, and the "Stop All" button works.

If you run things as an external tool, or shell script, IntelliJ doesn't know how to stop it.