Gradle Maven like multi module project -


when define multi module project in maven, have 1 root project , modules. when build root project, maven transitivelly builds modules in correct order. far pretty similar gradle.

but maven, can clone 1 submodule repository , build locally without need download whole project structure. because define dependencies on other modules within same project other external dependency , downloaded , cached local repository (nexus).

with gradle, define cross module dependencies compile project(':other'). need clone whole project structure repository in order resolve , build correctly. there way use gradle multi module project support, without having locally clone whole project structure?

i argue maven's multi-module support slapped on after-thought. unlike gradle, project dependency not first class concept. instead maven "reactor" substitutes local artifacts dependencies when gav (group/artifact/version) matches.

if you'd use same approach in gradle can specify dependencies using gav notation , use new composite build feature join 2 or more separate gradle builds , substitute repository dependencies local source dependencies. note that can define projects included in composite using groovy script based on custom logic (eg if subfolder exists in root folder etc)

note composite build support new feature added in gradle 3.1. prior gradle 3.1 can use prezi pride achieve same


Comments

Popular posts from this blog

aws api gateway - SerializationException in posting new Records via Dynamodb Proxy Service in API -

asp.net - Problems sending emails from forum -