Bug fix (non-breaking change which fixes an issue)
Refactor (non-breaking change which improves the structure or operation of the implementation)
Description
Freemarker wrapper now relies on its environment to control where stdout and stderr go.
"Generation successful" messages after each successful invocation of the freemarker engine are no longer logged.
Motivation and Context
Previously, the wrapper was always redirecting both stdout and stderr to the one target. With the changes to output handling in the wrapper and engine, the wrapper script now assumes the environment is set up to redirect output where required.
The logging of "generation successful" was removed to reduce the noise in the output generated during template creation.
Intent of Change
Description
Motivation and Context
Previously, the wrapper was always redirecting both stdout and stderr to the one target. With the changes to output handling in the wrapper and engine, the wrapper script now assumes the environment is set up to redirect output where required.
The logging of "generation successful" was removed to reduce the noise in the output generated during template creation.
How Has This Been Tested?
Local template generation
Followup Actions