support for proxy authentication fill-in added

[sealor]

When providing maven settings and global maven settings the proxy authentication is now also filled in using the Jenkins credentials if available.
The feature is similar to the authentication replacements for maven server configurations.

See https://maven.apache.org/settings.html

[sealor]

@imod
Do we need to create an JIRA issue before sending a pull-request?
We are longingly waiting for this proxy feature ;-)

[imod]

@sealor its not required per se, but it helps a lot to get more context about the issue you try to solve

[jonfreedman]

It would be great to get this merged

[imod]

@sealor I'm sure this will work, but from a users point of view, this is a hidden feature. To make this more visible (and clean), there should probably be a "Proxy Credentials" section beside the "Server Credentials" Section when editing a configuration.

this comes even more apparent when you look at the way this would look when creating a configfile with the job-dsl plugin:

configFiles {
    mavenSettingsConfig {
        id('DEFAULT_MAVEN_SETTINGS')
        name('default maven settings')
        comment('default settings for yooture projects')
        content(readFileFromWorkspace('config-files/maven-settings.xml'))
        isReplaceAll(true)
        serverCredentialMappings {
            serverCredentialMapping {
                serverId('private-release')
                credentialsId('MYUSER_MAVEN')
            }
            serverCredentialMapping {
                serverId('private-snapshot-repository')
                credentialsId('MYUSER_MAVEN_SNAPSHOT')
            }
        }        
    }
}

[sealor]

@imod Now, there is a "Proxy Credentials" section beside the "Server Credentials" section. The new feature behaves exactly like the other one.

[sealor]

@MRamonLeon
Why did you close this pull request?

I myself do not need this feature anymore because I now use another solution. But in my opinion this feature would be very helpful for others.

[MRamonLeon]

@sealor I was scrubbing a bit and I probably misunderstood your last comment and taking into account the last time it had activity I closed it. Happy to reopen if it's still interesting. I can't commit to any review ATM though.

[sealor]

@MRamonLeon
Thank you for re-opening this issue!
I did not know that there are conflicting files now. I plan to resolve them.