Better gradle project conventions #1684
Replies: 3 comments
-
Regarding auto-creation of In an effort to "simplify" the amount of overhead a user needs to do to create a registry project, it gets auto-created. IE, they don't need to modify settings.gradle or build.gradle to add a new registry project - and then it also implies the "proper naming" for various derived bits from I took this approach because I think there is only one important piece of project-level configuration: the simple name |
Beta Was this translation helpful? Give feedback.
-
I think moving into an opt-in rather than opt-out approach is good. I think trying to pare down our root build.gradle is a good goal for better maintainability long term. I've tried to establish some ways to do that via buildSrc plugins; for example, java-publishing-conventions. Getting rid of |
Beta Was this translation helpful? Give feedback.
-
Regarding subproject naming, Right now, I've opted to do Places of consideration: |
Beta Was this translation helpful? Give feedback.
-
Discussion from #1670, regarding gradle (sub)project conventions from @niloc132:
Two thoughts:
Beta Was this translation helpful? Give feedback.
All reactions