outputFile support for capturing exec not functional

I have uncommented the code related to output file, and it seems to work (at least on my project). Could someone explain what harm was the code causing (see the patch)?

Thanks.

Since the outputFile configuration does not work in 1.2, it should be removed from the documentation (http://mojo.codehaus.org/exec-maven-plugin/exec-mojo.html#outputFile). Having it in the docs implies that it works with the current version, which is not the case.

BTW, outputFile works fine after downgrading to 1.1.

The patch works great, thanks. <outputFile> is a great feature and it really should be re-enabled in trunk.

I agree with previous comments. <outputFile> is very useful. We use it to capture a Git commit hash into a file that is then merged into a manifest. Please add it back.

Why is this issue ignored when the fix is so simple?

Yes, this feature is badly needed. If I can capture output from SVN DIFF, I can use the Enforcer plugin to detect if any changes exist (file size). Commit this feature please!!!

Spent a whole day chasing down this bug, is there a maintainer of this code who reads these tickets?

Only those interested in the fix
I guess becoming maven committer is a way to go.

But it really feels like maven is going off the stage slowly, like all projects where no active development's being observed.

I've tried to discover why this was reverted. I can't imagine we revert things just for fun, there should be a good reason for it. Anyhow, it looks like a valid request to return the outputFile option.

I think there's something wrong with the original code: it looks like it mixes the output of Maven and the output of the executed program.
IMO the plugin should ignore the output of Maven and only focus on the executable output.
So there's some rewriting required.

I think I understand why this was reverted: the outcome very unpredictable. I've written an IT, which switches from stream (out and err) after every line of text. But in the outputfile you won't get the same order. Even if I call the flush() after every new line.
Maybe somebody has a good suggestion.

If it's not written in the correct order, we need to find some other solution.
Some ideas:

• Write System.out and System.err to separate files
• Buffer the System.err, and add it at the end of the file
• Add an option the specify a template for both output streams, like '[out] %s' and '[err] %s'
• Add a big fat note

WDYT?

@Robert: System.out and System.err do not form a linear stream; there is no way to reliably consolidate these two into a single file - even if you flush.

That's the way things work in real life, why do we suddenly start caring when we dump it to file ?

@Kristian,

that's how it should work in exec-maven-plugin-1.1, at least they tried but didn't succeed. I believe this feature request is valid, but the original solution was wrong.
So your suggestion is to create 2 output files? Sounds good to me, trying to hack around this issue doesn't feel right.

Actually I'm advoacting to keep 1 file, since that's the way things work in real life. I believe if you run your IT with output to the proper console, you'll get mixed order in the streams there too.... ("Incorrect" order)

Good enough, I'll go for a single file and a note. Do you know an official page I can refer to?

Any news on this?

thanks for the ping. It still needs to be implemented.