You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Rust code is built as part of the Maven build in the module compaction/compaction-rust. This is done with exec-maven-plugin.
We have scripts that run the Maven build using scripts/build/build.sh. This runs a quiet Maven build in the quick profile with the tests disabled. This suppresses most output, but not currently the logging from the Rust build.
Description
We'd like the Maven build to suppress output from the Rust build if it's run in quiet mode.
Background
The Rust code is built as part of the Maven build in the module
compaction/compaction-rust
. This is done with exec-maven-plugin.We have scripts that run the Maven build using
scripts/build/build.sh
. This runs a quiet Maven build in the quick profile with the tests disabled. This suppresses most output, but not currently the logging from the Rust build.Description
We'd like the Maven build to suppress output from the Rust build if it's run in quiet mode.
Analysis
The Rust build is done with cross-rs:
https://docs.rs/crate/cross/latest
From that page: "cross has the exact same CLI as Cargo but relies on Docker or Podman".
Cargo has a command line argument similar to Maven,
-q
or--quiet
:https://doc.rust-lang.org/cargo/commands/cargo-build.html
It's also possible to set this in an environment variable, CARGO_TERM_QUIET:
https://doc.rust-lang.org/cargo/reference/config.html
If we use an environment variable we will need to configure Cross to pass this through, see the documentation linked above.
We may be able to propagate this setting through from Maven. See the documentation for the Maven plugin:
https://www.mojohaus.org/exec-maven-plugin/usage.html
The text was updated successfully, but these errors were encountered: