Show full integration errors when verbose mode is active

[quintesse]

See #1475 (comment)

[maxandersen]

so I think not only are we hiding the exceptio but we are also not actually capturing error output. So can't actually see the true error anymore.

[filippor]

Yes the output is used to get the result. Maybe it is possible to use the error stream for errors or verbose log

[maxandersen]

this keeps biting me. it works when running internally. when external launch we don't capture error and no error reported.

i.e. have a broken pom.xml (syntax error) next to a main.java depending on quarkus and it will fail with no info if running with java8 but it has //JAVA 17+ ...and the root cause is that quarkus can't parse the pom.xml (which it shouldn't do but we should at least report why its failing)

[quintesse]

The reason this was never really implemented is because it's hard to determine what the error is. The integration code is completely free to write whatever it likes to stdout and stderr, so how do we pass an error back to the main process?

We could perhaps force any output to go to stdout only and use stderr for any errors, but that would mean the output might change depending on how the integration is run. That doesn't sound acceptable.

We could of course write the error to some known file but i really think that's a crappy solution. Can anybody come up with a better solution?

[quintesse]

Well, now that I think of it the external proces could simply write the error to stderr (if --verbose is set). That way the main process still isn't any the wiser but at least the user gets their error message.

[maxandersen]

Yeah. I would Think we just need to relay steder to stderr and stdout to stdout and just treat it like we do internal integration run.