java-caller - npm Package Compare versions

Comparing version 1.0.0-beta.0 to 1.0.0

CHANGELOG.md

 # Changelog
 
-## [1.0.0] UNRELEASED
+## [1.0.0] 2020-08-10
 
 Initial version

package.json

 {
   "name": "java-caller",
-  "version": "1.0.0-beta.0",
+  "version": "1.0.0",
   "description": "Library to easily call java from node sources. Automatically installs java if not present",
@@ -5,0 +5,0 @@ "main": "./lib/index.js",

README.md

 <!-- markdownlint-disable MD033 -->
 # Java Caller for Node.js
 
-- **WARNING: Initial development in progress**
-
 [![Version](https://img.shields.io/npm/v/java-caller.svg)](https://npmjs.org/package/node-java-caller)
@@ -42,3 +40,3 @@ [![Downloads/week](https://img.shields.io/npm/dw/java-caller.svg)](https://npmjs.org/package/node-java-caller)
 | mainClass          | If classPath set, main class to call                                                                                                                                  |                      | `"com.example.MyClass"`                  |
-| rootPath           | If classPath elements are not relative to the current folder, you can define a root path                                                                              | `.` (current folder) | `"/home/my/folder/containing/jars"`      |
+| rootPath           | If classPath elements are not relative to the current folder, you can define a root path. <br/> You may use `__dirname` if you classes / jars are in your module folder    | `.` (current folder) | `"/home/my/folder/containing/jars"`      |
 | javaExecutable     | You can force to use a defined java executable, instead of letting java-caller find/install one                                                                       |                      | `"/home/some-java-version/bin/java.exe"` |
@@ -107,2 +105,13 @@ | minimumJavaVersion | Minimum java version to be used to call java command.<br/> If the java version found on machine is lower, java-caller will try to install and use the appropriate one | `1.8`                | `11`                                     |
 
+## TROUBLESHOOTING
+
+Set environment variable `DEBUG=java-caller` before calling your code using java-caller module, and you will see the java commands executed.
+
+Example debug log:
+
+```shell
+java-caller Found Java version 1.80131 +1s
+java-caller Java command: java -Xms256m -Xmx2048m -cp C:\Work\gitPerso\node-java-caller\test\java\dist com.nvuillam.javacaller.JavaCallerTester -customarg nico +1ms
+```
+
 ## CONTRIBUTE
@@ -112,2 +121,2 @@
 
-Please follow [Contribution instructions](https://github.com/nvuillam/node-java-caller/blob/master/CONTRIBUTING.md)
+Please follow [Contribution instructions](https://github.com/nvuillam/node-java-caller/blob/master/CONTRIBUTING.md)

New alerts

License Policy Violation

License

This package is not allowed per your license policy. Review the package's license to ensure compliance.

Found 1 instance in 1 package

Fixed alerts

License Policy Violation

License

This package is not allowed per your license policy. Review the package's license to ensure compliance.

Found 1 instance in 1 package

No v1

Quality

Package is not semver >=1. This means it is not stable and does not support ^ ranges.

Found 1 instance in 1 package

Improved metrics

Total package byte prevSize

56988

increased by0.64%

Number of low quality alerts

0

decreased by-100%

Number of lines in readme file

120

increased by9.09%

No dependency changes