Wrong Gradle plugin dependency version

[Hari Sekhon]

On this project:

https://www.versioneye.com/user/projects/57616cdb0a82b20053182c74#tab-dependencies

The SonarQube Gradle plugin is definitely set to 2.2 but it still shows 2.0.1 outdated even though I changed that yesterday and I even re-parsed today and it's still the case.

[Robert Reiz]

@harisekhon The project was created through the API. I guess through the gradle-versioneye-plugin. Did you run the update goal on the plugin to push your current dependencies to the VersionEye API?

[Hari Sekhon]

I didn't realize I'd have to do this by hand each time, surely it should just read the latest build.gradle file from the last commit??

I've just tried to run the gradle versioneye plugin manually but got the following error:

./gradlew versionEyeUpdate
:versioneye-pom
:versioneye-update FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':versioneye-update'.
> javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.

BUILD FAILED

Total time: 4.118 secs
make: *** [gradle-versioneye] Error 1

[Robert Reiz]

Hi @harisekhon. If you create a project trough the API (Gradle Plugin), than VersionEye doesn't has any info about your SCM. That's the whole point of using the API and the Gradle Plugin. That way you can monitor projects without giving VersionEye access to your GitHub or Bitbucket account.

If you have issues with the Gradle Plugin please open a ticket on this repository: https://github.com/stempler/gradle-versioneye-plugin.