Similar to CODETOOLS-7901613.
Often javatest agent is started not directly but via a separate tool, script, framework. For example: jck4jdk, qatools, aurora, qagrid, etc.
The tool may have different set of options that non-trivially translated to
agent's options which are invisible (i.e. no way to see how exactly agent is invoked).
This request is to provide ability for javatest agent invoked from inside some tool
to print arguments that are passed to agent.
For example, printing argument can be triggered by a property:
-Djavatest.verbose=args
or something like that.
Often javatest agent is started not directly but via a separate tool, script, framework. For example: jck4jdk, qatools, aurora, qagrid, etc.
The tool may have different set of options that non-trivially translated to
agent's options which are invisible (i.e. no way to see how exactly agent is invoked).
This request is to provide ability for javatest agent invoked from inside some tool
to print arguments that are passed to agent.
For example, printing argument can be triggered by a property:
-Djavatest.verbose=args
or something like that.
- relates to
-
CODETOOLS-7901644 Argument logger doesn't display the -laf value
- Closed
-
CODETOOLS-7901613 logging/printing arguments harness started with
- Closed