Do not drop environment variables that contain '=' in their value, or have no value.

[AlanUnderwood]

I noticed whilst doing a little home project that this plugin will not pass environment variables to the java application from a script file if the environment variable in the script file has an '=' character in it. It silently ignores them.

This change will read environment variables that contain '=' characters and add them to the Java application's environment.
It will also include environment variables whose value is empty.
Finally, it will log a warning for any environment variables that are dropped, though I don't think it would ever happen because the 'env' command will always return
VAR=VAL
or
VAR=

[rmcuenen]

Is this ever going to be fixed in a release?
I actually need the first part of this issue:
VAR="VAL -ARG1=VAL1 -ARG2=VAL2"

[AlanUnderwood]

Any chance someone with the power could trigger this build again. I think the build failure was down to the build system at the time, not the code changes.

[dmatej]

Could you rebase it to current master? It uses old JDK versions, build passed on Oracle JDK8, but failed on JDK7. I see newer builds use OpenJDK.

[AlanUnderwood]

@dmatej PR branch rebased and everything seems to be working and tests passing. 😃

[AlanUnderwood]

Bump! Could this be merged please.

[AlanUnderwood]

@pzygielo @dmatej
Could this please be reviewed and merged.

[AlanUnderwood]

@dmatej Thanks! 🥳