RunJMeterMojo calls forceHeadless overriding intentional -Djava.awt.headless=false set by user

Hello @Ardesco ,

Great work on test coverage and code cleanup.

Reviewing changes, I notice a change.

Previously, if user had set:

-Djava.awt.headless=false

It was kept.

In master code now, forceHeadless removes and overrides to:

-Djava.awt.headless=true

Is this intentional ?

[Ardesco]

or if you want to only add RUN_HEADLESS if there is no headless setting you can do:

    private static final String HEADLESS_SETTING = "-Djava.awt.headless=";

    public JMeterProcessJVMSettings forceHeadless() {
        if (arguments.stream().noneMatch(argument -> argument.equals(HEADLESS_SETTING))) {
            arguments.add(RUN_HEADLESS);
        }

        return this;
    }

[pmouawad]

I added it to make plugin work on some docker that used headless jvms. So I think it is needed.

To summarize my intention:

• If user does nothing we add it
• If user set headless=false, we don’t override as he probably wants to work in non headless mode