Slackbot
10/11/2023, 6:51 PMVampire
10/11/2023, 6:58 PMVlastimil Brecka
10/12/2023, 9:00 PMVampire
10/12/2023, 9:12 PMapp1, app2 and lib where both appX use lib,
you would have one build for lib, one composite build for app1 that includes the build for lib and one composite build for app2 that also includes the build for lib.Vlastimil Brecka
10/12/2023, 9:19 PMlib developer)
-- if I were to rename a lib function, how would I do that? only way to have a composite build of all?Vlastimil Brecka
10/12/2023, 9:20 PMVampire
10/12/2023, 10:44 PMwell, my n1 benefit in the single build is that I can find usages across everythingBut that is exactly what you said you do not want. You said you only want to have in the IDE what you currently work on. Here you say you want everything in the IDE to find usages. You can hardly have both as they are contradictory. 😄
and being able to build everything easily if broke anything (me as theWell, you can of course have a composite build that then includesdeveloper)lib
app1 and app2 to be able to build both with one Gradle invocation.
And if you open that uber-composite build you also would have everything open and usable in the IDE, but can also just open app1 to only have app1 and its dependencies open.
anyways, as far as intellij goes, does each composite build behave as a separate project?Depends on what you mean exactly. You can open a composite build as project, yes, and that will open all the included builds too in the IDE within that project as source roots.
Vlastimil Brecka
10/14/2023, 11:32 AMVampire
10/14/2023, 12:01 PM