Hi I want to move some versions into a configurati...
# gradleb
Bernhard
12/04/2018, 9:44 AMHi I want to move some versions into a configuration so that I can use that in both buildSrc and src. I thought about moving it to the settings.gradle.kts. Does buildSrc have access to that and how do I use settings in my build.gradle.kts?
g
gildor
12/04/2018, 9:47 AMwhat is “src”? You want to use it on runtime of your application?
gildor
12/04/2018, 9:47 AMor you just want to use version in buildSrc/build.gradle?
b
Bernhard
12/04/2018, 9:48 AMI have deps that line up with my application and build (e.g. junit)
Bernhard
12/04/2018, 9:48 AMI don't want to bump the same version twice
g
gildor
12/04/2018, 9:49 AMYeah, there is easy way. Only parse some properties file in buildSrc/build.gradle and do the same in buildSrc/src
You can also parse only once, and set sytem property, but not sure that it’s good way
gildor
12/04/2018, 9:50 AMI would create an issue on Gradle issue tracker, looks as popular feature request
b
Bernhard
12/04/2018, 9:55 AMcan I name the properties file something other than project.properties?
Bernhard
12/04/2018, 9:55 AMg
gildor
12/04/2018, 9:55 AMYes, it can be any properties file
b
Bernhard
12/04/2018, 9:56 AMIs there something built in like: val kotlinVersion by properties("../file.properties")
g
gildor
12/04/2018, 9:56 AMthis file will not be parsed automatically. you have to do that manually (there is a class for that)
k
k_marussy
12/04/2018, 9:57 AMTo this I end I tend to generate source in buildSrc so the properties file only has to be parsed once (the main build.gradle.kts itself has the generated class on the classpath): https://github.com/FTSRG/theta/blob/750815bbdcedcd3826ddbcb3ddbc030280d7151b/buildSrc/build.gradle.kts#L46 I should probably extract this into a plugin, though.
g
gildor
12/04/2018, 9:57 AMYou need something like that
Properties().load(File("some.properties").reader())gildor
12/04/2018, 9:58 AMNot sure that this approach is better
b
Bernhard
12/04/2018, 10:01 AMthe whole thing would be a non issue for me if managing deps was as neat as in node.js (e.g. locking version ranges)
g
gildor
12/04/2018, 10:01 AMGradle has version locking and ranges
b
Bernhard
12/04/2018, 10:02 AMok, nvm then 🙂
g
gildor
12/04/2018, 10:02 AMgildor
12/04/2018, 10:04 AMNot exactly about versions, but just allow to have complicated resolution rules. Usual ranges is just about using wildcards for versions
https://docs.gradle.org/current/userguide/customizing_dependency_resolution_behavior.html
5 Views