mirror of
https://github.com/xpipe-io/xpipe.git
synced 2024-10-01 09:40:35 +13:00
Small fixes [release]
This commit is contained in:
parent
2d931ce1a4
commit
c91fe5b5c5
2 changed files with 2 additions and 7 deletions
|
@ -136,11 +136,7 @@ You can use the gradle wrapper to build and run the project:
|
||||||
To include this CLI executable in this build, make sure to run `gradlew buildCli` first
|
To include this CLI executable in this build, make sure to run `gradlew buildCli` first
|
||||||
- You can also run the CLI application in development mode with something like `gradlew :cli:clean :cli:run --args="daemon start"`.
|
- You can also run the CLI application in development mode with something like `gradlew :cli:clean :cli:run --args="daemon start"`.
|
||||||
Note here that you should always clean the CLI project first, as the native image plugin is a little buggy in that regard.
|
Note here that you should always clean the CLI project first, as the native image plugin is a little buggy in that regard.
|
||||||
- `gradlew <project>:test` will run the tests of the specified project.
|
- `gradlew <project>:test` will run the tests of the specified project.
|
||||||
|
|
||||||
Some production unit tests depend on a connection to an X-Pipe daemon to properly function.
|
|
||||||
To launch the installed daemon, it is required that you either have X-Pipe
|
|
||||||
installed or have set the `XPIPE_HOME` environment variable in case you are using a portable version.
|
|
||||||
|
|
||||||
You are also able to properly debug the built production application through two different methods:
|
You are also able to properly debug the built production application through two different methods:
|
||||||
- The `app/scripts/xpiped_debug` script will launch the application in debug mode and with a console attached to it
|
- The `app/scripts/xpiped_debug` script will launch the application in debug mode and with a console attached to it
|
||||||
|
@ -150,7 +146,6 @@ You are also able to properly debug the built production application through two
|
||||||
Note that when any unit test is run using a debugger, the X-Pipe daemon process that is started will also attempt
|
Note that when any unit test is run using a debugger, the X-Pipe daemon process that is started will also attempt
|
||||||
to connect to that debugger through [AttachMe](https://plugins.jetbrains.com/plugin/13263-attachme) as well.
|
to connect to that debugger through [AttachMe](https://plugins.jetbrains.com/plugin/13263-attachme) as well.
|
||||||
|
|
||||||
|
|
||||||
### Development FAQ
|
### Development FAQ
|
||||||
|
|
||||||
##### Why are there no GitHub actions workflows or other continuous integration pipelines set up for this repository?
|
##### Why are there no GitHub actions workflows or other continuous integration pipelines set up for this repository?
|
||||||
|
|
|
@ -47,7 +47,7 @@ public abstract class ProcessControlProvider {
|
||||||
localProcessControlProvider.command(parent, command, terminalCommand))
|
localProcessControlProvider.command(parent, command, terminalCommand))
|
||||||
.filter(Objects::nonNull)
|
.filter(Objects::nonNull)
|
||||||
.findFirst()
|
.findFirst()
|
||||||
.orElseThrow();
|
.orElse(null);
|
||||||
}
|
}
|
||||||
|
|
||||||
public static ShellProcessControl createSsh(Object sshStore) {
|
public static ShellProcessControl createSsh(Object sshStore) {
|
||||||
|
|
Loading…
Reference in a new issue