use client env vars

[delanym]

This plugin is not marked as thread-safe, but even when I select -T1 it fails with

[INFO] --- maven-jarsigner-plugin:3.0.0:sign (sign) @ project ---            
[WARN] Please specify alias name

My sign goal is configured with <alias>${env.SIG_ALIAS}</alias> but Im unable to mvnd help:evaluate to see if its being picked up.

[gnodet]

Can you try with mvnd help:evaluate -Dexpression=env.SIG_ALIAS -DforceStdout -q ?

➜  ~ export SIG_ALIAS=foo                                              
➜  ~ mvnd  help:evaluate -Dexpression=env.SIG_ALIAS -DforceStdout -q
[INFO] [stdout] foo
➜  ~ 

[delanym]

Thanks, I can't replicate the initial warning anymore and your command does output the variable.

It seems there's another issue though: this only works with a project that doesn't have modules, or by adding -N switch.

[ERROR] java.lang.IllegalStateException: Unknown project groupx:artifactx:versionx, found [groupy:artifacty:versiony]

[delanym]

It looks like env. refers to the daemon's environment—I tried un-setting a variable and it still found it. I can't think why I'd ever want the daemon env vars over the client.

[gnodet]

It looks like env. refers to the daemon's environment—I tried un-setting a variable and it still found it. I can't think why I'd ever want the daemon env vars over the client.

The daemon environment is supposed to be overriden by the client env vars before actually performing the maven build, but it does not seem to work as intended.

[gnodet]

The environment is correctly set, but the evaluation is done on system properties and there is a cache of the environment variables. I've worked around the problem in #451.

I still need to investigate why the -N option is required...

[gnodet]

I've raised #464