Gradle analysis didn't take in account gradle.properties file

[Nikolay Lagutko]

Hi I tried to use versioneye on one of my projects and it fails due to build structure of my project.

My build configuration is splitted on two files: build.gradle (dependencies, plugin configs etc.) and gradle.properties (version and some other info). For example

build.gradle:

dependencies {
    compile group: 'junit', name: 'junit', version: junitVersion
}

gradle.properties:

junitVersion = 4.12

And when I start analysis it should me alert with text:

ERROR: Could not find a single dependency in the project

To check my idea about non-analysing gradle.properties file I move versions to build.gradle:

dependencies {
    compile group: 'junit', name: 'junit', version: '4.12'
}

And analysis finished successfully.

So the question for you - is it possible to include gradle.properties file into gradle dependency analysis?

[M. P. R]

same here with gradle 2.3

ext {
    springVersion     = '4.1.5.RELEASE'
    seleniumVersion   = '2.45.0'
}
..
 compile "org.springframework:spring-context:${springVersion}"  

.. will show as locked "springVersion"** in table and therefore "outdated".

Seen Screenshot on https://totask2.wordpress.com/2015/03/21/track-dependency-versions-with-versioneye/

[Robert Reiz]

Please use the Gradle VersionEye Plugin for this: https://github.com/stempler/gradle-versioneye-plugin