are zou using implementation, api or compile depen...
# gradlen
Nikky
11/19/2018, 9:49 AMare zou using implementation, api or compile dependency ?
j
janvladimirmostert
11/19/2018, 9:50 AMoh, is that what that implementation is for, i guess that should be `compile then
n
Nikky
11/19/2018, 9:50 AMapi
j
janvladimirmostert
11/19/2018, 9:50 AMwhat is api for ?
n
Nikky
11/19/2018, 9:51 AMit exposes the module to consumers of the library
Nikky
11/19/2018, 9:51 AMother alternative is to add
jvaas-providerNikky
11/19/2018, 9:52 AMbut that kind of clutters the dependency graph
j
janvladimirmostert
11/19/2018, 9:53 AMis the stuff inside
settings.gradle.ktsn
Nikky
11/19/2018, 9:53 AMinclude ? yes
Nikky
11/19/2018, 9:54 AMotherwise gradle will not be able to find the subprojects..
j
janvladimirmostert
11/19/2018, 9:54 AMok
should that be
include("../jvaas-provider")include("jvaas-provider")janvladimirmostert
11/19/2018, 9:55 AMall the modules are on the same level in the root directory
n
Nikky
11/19/2018, 9:55 AMbut zou have a root project right ?
j
janvladimirmostert
11/19/2018, 9:55 AMwell, these are just loose modules, there's not really a root project
janvladimirmostert
11/19/2018, 9:56 AMfor the prototype i added a settings.gradle.kts with this in it
Copy code
rootProject.name = "jvaas-platformn
Nikky
11/19/2018, 9:56 AMwell in which level lies your gradlew binary ?
j
janvladimirmostert
11/19/2018, 9:56 AMeach of these modules have their own
n
Nikky
11/19/2018, 9:57 AMi doubt that will work
j
janvladimirmostert
11/19/2018, 9:58 AMeach of them needs to be compilable on their own, there might be 200 of them soon. In maven it meant having to compile each individual one every time you do a clean checkout
n
Nikky
11/19/2018, 9:58 AMyou can compile submodule on their own via eg.
gradlew :submodule:buildNikky
11/19/2018, 9:59 AMand it will just recompile the other submodules it depends on
j
janvladimirmostert
11/19/2018, 10:00 AMok, so should i create a build.gradle.kts in the root then?
these modules should also be accessible to outside projects without bringing in all 200 of them
e
eskatos
11/19/2018, 10:45 AMIf what you’re looking for is replacing the need for maven snapshots in the maven local repository maybe Gradle’s composite builds will help. It allows you to connect otherwise independent gradle builds (may they be single or multi-project).
j
janvladimirmostert
11/19/2018, 10:51 AMcomposite builds looks promosing, let me try that and see if it works
janvladimirmostert
11/19/2018, 10:58 AMYay, that works, just had to change my
settings.gradle.kts Copy code
includeBuild("../jvaas-provider")🎉 1
5 Views