- edited description
problem when using variables for versions
Issue #147
resolved
for deduplication reasons I use variables like this:
final DAGGER_VERSION = '2.0.2'
dependencies {
apt "com.google.dagger:dagger-compiler:${DAGGER_VERSION}"
androidTestApt "com.google.dagger:dagger-compiler:${DAGGER_VERSION}"
compile "com.google.dagger:dagger:${DAGGER_VERSION}"
}
but then it shows up in VersionEye like this:
dagger $ 2.0.2 Follow
dagger-compiler $ 2.0.2 Follow
dagger-compiler $ 2.0.2 Follow
Comments (6)
-
reporter -
You can find out about reasons why developers will do this in this talk.
-
- changed status to resolved
@mrligi @tbsprs Should be fixed now. Please click the "re parse now" button for your project and confirm that it works like expected.
-
Please note, that people tend to define those version variables in other files such as gradle.properties which are then available globally via
project.supportLibVersion
referering to the example in the screenshot. -
reporter Unfortunately it is not working for me :-(
still see:
Dependency Resolved Newest
dagger $ 2.0.2for project gobandroid
-
I'm using a lot of this kind of trick:
And I can't see them :-/
- Log in to comment