- Fix problems with unresolvable configurations introduced in Gradle 3.4
- Add support for connecting to VersionEye via a proxy
- Support for including sub-project dependencies
- Added tasks for security and license checks
- Support association to an organisation and team when creating a VersionEye project
- Don't override comments in
gradle.properties
when creating a VersionEye project - Support for determining dependencies to Gradle plugins
- Generate a
pom.json
instead of apom.xml
for upload to VersionEye - Derive dependency scopes from dependency configuration names
- Define API key via
VERSIONEYE_API_KEY
environment variable (only if Gradle property is not defined) - Added plugin task group and task descriptions
- Improved error reporting for failed requests to the VersionEye API
- Support customizing base URL for use with VersionEye Enterprise
- Fix for breaking VersionEye API change (Project key is obsolete)
- Qualified plugin ID (
org.standardout.versioneye
) for use with new Gradle plugin repository - #2 Increased log level to lifecycle and added more logging on update
- Fixed failure when build directory was not present