sridharv 891bb03169 Replace the generated jar atomically
Fixes #8

This change creates a temporary file in the directory of the target jar.
The temporary file contains the generated jar and is atomically
renamed to the actual jar.

Thanks to @arfan for reporting this bug.
2018-01-17 16:47:47 +01:00
2016-03-28 19:57:19 +02:00
2016-11-12 22:08:30 +01:00
2018-01-17 16:47:47 +01:00
2016-03-27 19:53:45 +02:00

GoJava - Java bindings to Go packages Build Status

GoJava uses a forked version of gomobile to generate Java bindings to Go packages. The same set of types are supported. Details on how the binding works can be found here.

Usage

	gojava [-v] [-o <jar>] [-s <dir>] build [<pkg1>, [<pkg2>...]]

	This generates a jar containing Java bindings to the specified Go packages.

	-o string
	    Path to write the generated jar file. (default "libgojava.jar")
	-s string
	    Additional path to scan for Java source code. These files will be compiled and
	    included in the final jar.
	-v  Verbose output.

You can include the generated jar in your build using the build tool of your choice. The jar contains a native library (built for the build platform) which is loaded automatically. Cross platform builds are not currently supported.

NOTE: This has only been tested on an OSX developer machine and Linux (on Travis) and not in production.

Description
GoJava - Java bindings for Go packages
Readme Apache-2.0 120 KiB
Languages
Go 77.1%
Java 22.9%