Closed sghpjuikit closed 5 years ago
Please do not call it "root" but "player", root is ambiguous as we.
Blocked by creating buildSrc build, which will split off utility portion of the builds into standalone build, where custom tasks will also reside.
I attempted to split the build file but failed to work it out. I'm putting this off for now. Very low priority.
Yeah, things like these are what I do when I get bored, so I'd assign this to me and do it sometime 😉
Thx
I realized you have put certain tasks (buil, run, ...) into a main group. Is there any reason for this other than covnenience?
My real question however is that assuming we split the main build file into that for allprojects and main module, which module should have application plugin and the run task?
I realized you have put certain tasks (buil, run, ...) into a main group. Is there any reason for this other than covnenience?
No, only for convenience, so that you can directly find the most important task in the IDE.
My real question however is that assuming we split the main build file into that for allprojects and main module, which module should have application plugin and the run task?
I would put the run task into the root file, or have it in the player and then add a run task to the root that delegates to the player, kind of a taste thing.
I see. So I was on the right track, just lacked the skill to finish through.
kotlinc task that downloads kotlin compiler is now removed. This is handled in runtime by the application itself. See #174
Closing as non-issue. Any improvements in build will be done when needed.
I used idea
gradle plugin to set up out
as an excluded
directory for widget modules. This solves some of the IDE warnings, like class already declared.
This is umbrella issue for all gradle-project-structure things.
1 Having gradle build files in one location is against convention. Do we move build files? Where?
2 The first improvement I suggest is to create a player subproject to let the root project encapsulate the entire project and nothing else. Right now
project.gradle.kts
fulfills 2 roles. So:project.gradle.kts
becomes place to setup common build configuration, likeallprojects {}
root.gradle.kts
becomes place to set up player module exclusively