gradle-execfork-plugin | gradle plugin that lets you define Exec | Plugin library

by psxpaul Kotlin Version: 0.1.4 License: Apache-2.0

X-Ray Key Features Code Snippets(1)Community Discussions(1)Vulnerabilities Install Support

kandi X-RAY | gradle-execfork-plugin Summary

gradle-execfork-plugin is a Kotlin library typically used in Plugin, Gradle applications. gradle-execfork-plugin has no vulnerabilities, it has a Permissive License and it has low support. However gradle-execfork-plugin has 8 bugs. You can download it from GitHub.

A gradle plugin that lets you define Exec and JavaExec tasks that run in the background

Support

Quality

Security

License

Reuse

Support

gradle-execfork-plugin has a low active ecosystem.

It has 42 star(s) with 17 fork(s). There are 5 watchers for this library.

It had no major release in the last 12 months.

There are 7 open issues and 25 have been closed. On average issues are closed in 117 days. There are 2 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of gradle-execfork-plugin is 0.1.4

Quality

gradle-execfork-plugin has 8 bugs (8 blocker, 0 critical, 0 major, 0 minor) and 45 code smells.

Security

gradle-execfork-plugin has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

gradle-execfork-plugin code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

gradle-execfork-plugin is licensed under the Apache-2.0 License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

gradle-execfork-plugin releases are available to install and integrate.

Installation instructions are not available. Examples and code snippets are available.

It has 918 lines of code, 64 functions and 27 files.

It has low code complexity. Code complexity directly impacts maintainability of the code.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of gradle-execfork-plugin

Get all kandi verified functions for this library.

gradle-execfork-plugin Key Features

No Key Features are available at this moment for gradle-execfork-plugin.

gradle-execfork-plugin Examples and Code Snippets

gradle-execfork-plugin,Usage

Kotlin

Lines of Code : 32

License : Permissive (Apache-2.0)

Copy

plugins {
  id 'com.github.psxpaul.execfork' version '0.1.13'
}

task startDaemon(type: com.github.psxpaul.task.ExecFork) {
    executable = './MainScript.sh'
    args = [ '-d', '/foo/bar/data', '-v', '-l', '3' ]
    workingDir = "$projectDir/src/mai

Community Discussions

Trending Discussions on gradle-execfork-plugin

How can I configure gradle to start and stop spring boot microservices that stay alive after build completion?

QUESTION

How can I configure gradle to start and stop spring boot microservices that stay alive after build completion?

Asked 2017-Jul-20 at 19:13

I'm developing an application server that relies on two emulators configured as spring boot microservices. We've recently extracted the emulators from the root project into a separate repository, as they're being used by some other projects as well, and this works a little nicer for inter-project maintenance. I would like to be able to run these emulators from the main project root, as opposed to having to check out their repository and run from that directory. We do something like this for our gradle integration tests - we're using ExecFork (https://github.com/psxpaul/gradle-execfork-plugin) to fire up the two processes. The problem here is that the processes die when the build completes.

What I'm looking for is something similar to this, so that I can run e.g. ./gradlew startEmulators and have both emulators check out the specified version and either block the gradle task (taking up the command window, ctrl-c to stop) or outlive the gradle task. The ability to stop them would be handy as well, but that's a would-like rather than a must-have at this point.

I'll take solutions alternative to gradle too, but preferably nothing too complicated - this needs to be something that I can fairly simply blast out instructions for to the dev team

...

ANSWER

Answered 2017-Jul-20 at 19:13

The answer ended up being a little janky, but it works. Basically, it looks like this:

Source https://stackoverflow.com/questions/45145109

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install gradle-execfork-plugin

You can download it from GitHub.

Support

Optional. The path of the working directory to run the executable from. This is treated as a relative path, so specifying an absolute path should be preferred. Default: project.projectDir.absolutePath. Optional. A list of arguments to give to the executable. Optional. The path of the file to write standard output to. If none is specified, process output is written to gradle's console output. Optional. The path of the file to write error output to. If none is specified, the error output is directed to the same destination as the standard output. Optional. A port number to watch for to be open. Until opened, the task will block. If none is specified, the task will return immediately after launching the process. Optional. A string to look for in standardOutput. The task will block until this pattern appeared or the timeout is reached. If not specified, the task will return immediately after launching the process. Optional. The maximum number of seconds associated with the waitForPort or waitForOutput task. Default: 60. Optional. A task that, when finished, will cause the process to stop. If none is specified, the process will stop at the very end of a build (whether successful or not). Required. The path to the executable. Two Strings OR one Map<String, String>. Optional. Environment variables to launch the executable with. You can either assign a Map with the '=' operator, or pass 2 Strings as key/value to the function. Note that multiple calls to this function are supported. Optional. Kills the process foricbly. Forcible process destruction is defined as the immediate termination of a process, whereas normal termination allows the process to shut down cleanly. Optional. Kill all descendents of the started process. Default: true. Optional. The path of the working directory to run the executable from. This is treated as a relative path, so specifying an absolute path should be preferred. Default: project.projectDir.absolutePath. Optional. A list of arguments to give to the executable. Optional. The path of the file to write standard output to. If none is specified, process output is written to gradle's console output. Optional. The path of the file to write error output to. If none is specified, the error output is directed to the same destination as the standard output. Optional. A port number to watch for to be open. Until opened, the task will block. If none is specified, the task will return immediately after launching the process. Optional. A string to look for in standardOutput. The task will block until this pattern appeared or the timeout is reached. If not specified, the task will return immediately after launching the process. Optional. The maximum number of seconds associated with the waitForPort or waitForOutput task. Default: 60. Optional. A task that, when finished, will cause the process to stop. If none is specified, the process will stop at the very end of a build (whether successful or not). Required. The classpath to use to launch the java main class. Required. The qualified name of the main java class to execute. Optional. The list of arguments to give to the jvm when launching the java main class. Two Strings OR one Map<String, String>. Optional. Environment variables to launch the java main class with. You can either assign a Map with the '=' operator, or pass 2 Strings as key/value to the function. Note that multiple calls to this function are supported. Optional. Kills the process foricbly. Forcible process destruction is defined as the immediate termination of a process, whereas normal termination allows the process to shut down cleanly. Optional. Kill all descendents of the started process. Default: true.

Find more information at: