This is a well know use case especially for Unix and Linux users: a software or script produces messages or any other kind of output and writes it directly to the process standard output stream (stdout). That stream can be redirected to a file or streamed as input into another process, creating nice pipelines. From the Windows world this is less famous, though an integral part of writing batch scripts.
An Explanation
Now medini is is a standard Windows GUI application, and not a command-line console application. As a result, it is not straight forward to capture the output of the program. Note: The usage of -debug or -dev brings up a command like window and shows the output stream. However, it still cannot be captured with Windows own mechanisms of redirecting the process output.
A Solution
To overcome this limitation, the eclipse ecosystem provides a separate launcher. The mediniAnalyze.exe is basically just a simple launcher program hat starts the right JVM, passing the right parameters etc. It is simply a renamed version of eclipse.exe. There is now a second launcher named eclipsec.exe which in contrast is a console application. We do not ship it by default as it is usually not required by standard users who simple launch the tool from the start menu. However, renaming eclipsec.exe to mediniAnalyzec.exe is the trick. Note that the launcher checks for an ini file with the same name as the executable. So eclipse.exe is loading the eclipse.ini while mediniAnalyze.exe is loading the mediniAnalyze.ini. The eclipsec.exe is still loading the eclipse.ini and mediniAnalyzec.exe the mediniAnalyze.ini file.
An Application
You can copy the attached and prepared mediniAnalyzec.exe at the same location as the mediniAnalyze.exe and use it the same way as the other launcher. If you do not have the right permission to save the file in the installation directory you may use the following command line instead:
eclipseOrOtherName.exe --launcher.ini C:\...\mediniAnalyze.ini
