#3140: Save error message

[levBagryansky]

Closes #3140

---

PR-Codex overview

The focus of this PR is to enhance the Rust build process in the Maven plugin by introducing new features and improvements.

Detailed summary

• Added WeHaveCargo as an execution condition for Rust builds
• Modified exception handling in BuildFailureException
• Updated Rust build process in RustNode class
• Added new tests for Rust build failures and error messages

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

[levBagryansky]

@maxonfjvipon WDYT

[levBagryansky]

@maxonfjvipon please check

[maxonfjvipon]

@levBagryansky LGTM!

[yegor256]

@levBagryansky did you try to use .withRedirect(true) of Jaxec, as explained here?

[levBagryansky]

@yegor256 Yes, it still did not print it.

[yegor256]

@levBagryansky we should find out, why it doesn't print. Most probably, something is wrong with the configuration of logging levels in log4j.properties file. Just throwing away the library and re-implementing its functionality is not a good practice.

[levBagryansky]

@yegor256 log4j.properties are configured right, and Jaxec has error message inside, in result.stdout(). The problem is that this message is not attached to Exception in line https://github.com/yegor256/jaxec/blob/master/src/main/java/com/yegor256/Jaxec.java#L365 so we cannot get it.

[yegor256]

@levBagryansky why it's important to put entire stdout into an exception (pretty unusual practice) instead of just sending it to the console/log? What do you mean by "we cannot get it"? If you can see the stacktrace (printed to stderr), you should see the log printed to stdout, I believe.

[levBagryansky]

@yegor256 because usually we would not like to see logs for all cargo projects. There are several inserts in eo program so logs from them would be mixed.

[levBagryansky]

@yegor256 We would like to get stdout & stderr of the process as String as the result of Jaxec::execUnsafe. Then we would print this String to log. But the problem is that execUnsafe does not return the String in case of exception, and it does not wrap it to Exception.
Looks like the only way to use Jaxec is to print stdout continuously. But then the log will be too unreadable, since many cargo processes will print their stdout at the same time.