Possible enhancement of jtreg : consolidate and simplify the MUST HAVE options when calling java or java tools in shell

[Jonathan Gibbons]

I would prefer to move people away from using shell scripts, so I don't 
see there is a need to rationalize these options.

-- Jon


On 02/11/2014 08:00 AM, michael cui wrote:
> Hi Jon,
>
> As you may notice, both dev and qa team put lots effort on enforcing 
> the general rule of passing some necessary options (such as vm 
> options) when calling java or java tools in shell script. Thanks a lot 
> for explaining the usage for team from time to time.
>
> Based on some discussion we have had, team feel now might be good time 
> to discuss about the possible enhancement of jtreg : consolidating 
> some of the options to simplify options that should be passed.
>
> The specific options we are referring now are two groups listed as 
> below :
>
> 1. TESTVMOPTS and TESTJAVAOPTS options when calling java from shell.
>
> If we could consolidate these two into one, that would be much more 
> intuitive, less confusing and easy to remember and follow.
>
> 2. TESTTOOLVMOPTS options for java tools such as javac, jar, 
> jarsigner, etc.
>
> Is it really necessary to make it as a must have options for calling 
> tools like javac, jar, etc in shell? In most general cases, what would 
> be hurt if it isn't there?
>
> We want to explore the possibility to simply those two places on 
> harness level. Please share your thoughts.
>
> Thanks,
> Michael Cui
>
>
>
>
>
>
>
>