diff options
| author | Fabian Meumertzheim <fabian@meumertzhe.im> | 2022-10-19 13:57:40 +0200 |
|---|---|---|
| committer | Fabian Meumertzheim <fabian@meumertzhe.im> | 2022-10-21 14:11:54 +0200 |
| commit | f96b872b053a23b64fae716ed2fbfc4f0708b5d3 (patch) | |
| tree | f14297fd770107478f2ab46c7b9a602b5ec872a2 /examples | |
| parent | 2c1c4d4134f1bb1532eb516b2a9917b8b7a5c55b (diff) | |
| download | jazzer-api-f96b872b053a23b64fae716ed2fbfc4f0708b5d3.tar.gz | |
driver: Fix and verify `jazzer` artifact
`java_export` targets build deploy jars that bundle all implicit
dependencies. Since `java_binary`'s `deploy_env` attribute excludes
entire Bazel targets rather than individual classes, this doesn't work
if only intend to bundle parts of `java_export` target - in this case,
the fuzz target API but not the hook API.
Instead, we revert the main `api` target an ordinary `java_library` and
verify correct contents right on the jar we deploy to Maven.
Diffstat (limited to 'examples')
| -rw-r--r-- | examples/BUILD.bazel | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/examples/BUILD.bazel b/examples/BUILD.bazel index ff1df42e..293fe6da 100644 --- a/examples/BUILD.bazel +++ b/examples/BUILD.bazel @@ -45,7 +45,7 @@ java_jni_library( ], visibility = ["//examples/src/main/native/com/example:__pkg__"], deps = [ - "//agent/src/main/java/com/code_intelligence/jazzer/api", + "//deploy:jazzer-api", ], ) @@ -333,7 +333,7 @@ kt_jvm_library( "src/main/java/com/example/KlaxonFuzzer.kt", ], deps = [ - "//agent/src/main/java/com/code_intelligence/jazzer/api", + "//deploy:jazzer-api", "@maven//:com_beust_klaxon", ], ) |