SCM credentials via env about unleash-maven-plugin

[shillner]

also support PK passphrase via env

[shillner]

maybe use existing parameters and support something like @{env.username}
is ${env.username} already resolved by maven?

[jgangemi]

there is a specific maven property for that. i'm using it somewhere, let me find it...

[jgangemi]

${user.name}

[shillner]

${user.name} refers to the name of the current OS user. I think this wouldn't be the right one for SCM access. Also there must be env variables for password and ssh passphrase available. I'm currently thinking about these ones and further options ;)

[jgangemi]

you asked if maven resolved ${env.username} - it does as ${user.name} :)

wouldn't these be one and the same 99% of the time? for the others you could probably override ${user.name} w/ a -D

[shillner]

No, you misunderstood. I didn't ask that, it was just a reminder for myself to try out different options for setting the username and password by just referring to an env variable. Sure, you can use the user.name variable if this one matches ;) Montag, 22 August 2016, 03:45nachm. +02:00 von Jae Gangemi [email protected] :

you asked if maven resolved ${env.username} - it does as ${user.name} :)
wouldn't these be one and the same 99% of the time? for the others you could probably override ${user.name} w/ a -D
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub , or mute the thread .