Fixed issues with Proxy Authentication

This release is fixing issue #80. Now the Proxy Authentication is working fine. Beside that it's possible to configure the Proxy settings in environment variables:

• VERSIONEYE_PROXY_HOST
• VERSIONEYE_PROXY_PORT
• VERSIONEYE_PROXY_USER
• VERSIONEYE_PROXY_PASSWORD

That way it can be configured outside of the source code.

Improved support for transitive dependencies

This releases improves the implementation of this configuration option:

<transitiveDependencies>true</transitiveDependencies>

Now this option will collect ALL transitive dependencies with RUNTIME scope. That means transitive dependencies with TEST or PROVIDED scopes are ignored.

Improved Update and Merge

This update brings 3 improvements:

• ADD: Now the project license is read from the pom.xml file and added to the pom.json. Now the project license is displayed in the web interface as well.
• CHANGE: Merging sub projects into the parent project was done by GAV. That caused some problems because it was not always unique. It is possible that the same parent project is monitored twice by VersionEye. The new merge method relies only on the unique Project IDs from the VersionEye API. That is much more reliable.
• BUGFIX: The goal mvn versioneye:update didn't work if a new module was added to an existing Maven reactor project. That is fixed now. The current version will simply create a new project for the newly added module and merge it into the parent project at VersionEye.

Add VERSIONEYE_BASE_URL

This release is bringing 3 changes:

• ADD: Up to now the baseUrl for the API had to be configured in the pom.xml file. Now it is possible to configure the baseUrl in the ENV variable VERSIONEYE_BASE_URL and in the versioneye.properties files.
• CHANGE: Default lifecycle phase to LifecyclePhase.VERIFY.
• BUGFIX: Plugins have been ignored in projects without Maven dependencies. This is fixed now.

Improve fetching of project_id

This release is improving the fetching of project_ids and has a better logging if the project_id can't be found.

Transitiv Dependencies

This new release brings a new feature to the plugin. Now with this optional configuration parameter:

<transitiveDependencies>true</transitiveDependencies>

the plugin will resolve ALL direct AND transitive dependencies and send all of them to the VersionEye API. By default this is turned off. This configuration option also has some implications to other configuration options. If transitiveDependencies is true then the configurations options ignoreDependencyManagement and skipScopes are ignored.

Add project.version to pom.json

This version adds the MavenProject.version to the pom.json, which is send to the VersionEye API. That way the server can display and handle the project version for Maven projects.

BugFix for missing versioneye.properties files

Version 3.9.0 had the bug that it didn't create the versioneye.properties file on mvn versioneye:create. That is fixed in this release!

Proxy Settings from versioneye.properties

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.

Skip DependencyManagement & mvn versioneye:delete

This release brings 3 additional features!

• ignoreDependencyManagement: Now there is a new configuration property ignoreDependencyManagement. If it is true this plugin will skip dependencies which are defined in the DependencyManagement part of the pom.xml. By default this property is false to keep the backward compatibility!
• mvn versioneye:delete: This new goal deletes the project from the VersionEye server and also deletes the versioneye.properties files locally from the project.
• output out-dated dependencies: Now the goals mvn versioneye:create and mvn versioneye:update output all out-dated dependencies in the console like in this example: