Skip to content

Proxy Settings from versioneye.properties
Compare
Choose a tag to compare
@reiz reiz released this 29 Feb 19:54
· 84 commits to master since this release
3.9.0
3942c6a

This release brings 2 new features!

Proxy Settings
Until now the proxy settings could be configured directly in the pom.xml file in the plugin configuration part. Now the configuration for the proxy can be placed at ~/.m2/versioneye.properties as well. That way it's centralised and not all projects need to configure it on their own. Just put the proxy settings into the ~/.m2/versioneye.properties file like this:

proxyHost=PROXY_HOST
proxyPort=PROXY_PORT
proxyUser=PROXY_USER
proxyPassword=PROXY_PASSWORD

If a project configures the proxy in the pom.xml in the configuration part of the plugin, that values are taken for that project. But otherwise the plugin will look for proxy settings at ~/.m2/versioneye.properties.

API KEY Settings
Until now the API Key could be configured in the pom.xml file in the plugin configuration part or in the versioneye.properties file. Now the API Key can be set as environment variable as well. Simply set it like this:

export VERSIONEYE_API_KEY=my_secret_api_key

Beside that the API Key settings are hierarchical now! The plugin will look for the API Key at this places in that order:

  • Environment variable VERSIONEYE_API_KEY
  • ~/.m2/versioneye.properties
  • src/qa/resources/versioneye.properties
  • src/main/resources/versioneye.properties
  • pom.xml file

That means if the environment variable VERSIONEYE_API_KEY is set, it can be overwritten by the ~/.m2/versioneye.properties file. And that can be overwritten by the settings in src/qa/resources/versioneye.properties and so on.

Assets 2
Loading