davidstanke / deprecated--tensorflow Goto Github PK

The Java code depends on C++ as a native library, provided as part of java arguments. Therefore, a rebuild of C++ code shouldn't force rebuild of the Java wrapper, but it seems to.

To demonstrate Bazel's efficiency against a large codebase, add more sources/targets. Maven will process them all while Bazel won't.

Running bazel test ... should invoke the tests for the C++ code, but it seems only to build it.

Currently, this fails in two ways: 1) unable to find specified image file; 2) Unable to invoke tensorflow.

I want to be able to run the app without creating a deploy jar (b/c I want the output of a test run to be the runnable artifact). So either we make bazel run work, or we make it so a non-deploy jar can be run via java -jar [...]

When running the application, TF may emit an error saying that it hasn't been compiled with support for everything that the host provides. Either squelch this message, or recompile more native.

Currently, changes to any Java file in Apache Commons causes Bazel to re-run all Java tests (bad deps I think). Make this more granular.

(kind of a cheat to ensure that remote exec won't be blocked on long-running java compile step)