How to organize build.gradle files and class structure in gradle project?
I want to make a plugin for teamcity and jenkins, but i'm not sure how I should be structuring my project to best fit that.
I've seen examples where there are multiple build.gradle files at various levels of the project, but some plugin/dependency definitions seem redundant between them as opposed to being in a more top-level build.gradle (if that makes sense). I'm not familiar with gradle or java at all. Any pointers would be incredibly helpful!
I also don't know how classes should be structured in a gradle project. I know there may be differing methodologies here, but I'm thinking the project structure might look like this:
Or something like that.
Subproject1 might be the actual server-side integration layer of the plugin, whereas subproject2 might be a webserver that is run separately outside of jenkins. Should those be in separate repositories?
Again any advice, resources or suggestions would be greatly appreciated!
I've seen examples where there are multiple build.gradle files at various levels of the project, but some plugin/dependency definitions seem redundant between them as opposed to being in a more top-level build.gradle (if that makes sense). I'm not familiar with gradle or java at all. Any pointers would be incredibly helpful!
I also don't know how classes should be structured in a gradle project. I know there may be differing methodologies here, but I'm thinking the project structure might look like this:
Or something like that.
Subproject1 might be the actual server-side integration layer of the plugin, whereas subproject2 might be a webserver that is run separately outside of jenkins. Should those be in separate repositories?
Again any advice, resources or suggestions would be greatly appreciated!
