Gradle Multi-Project Builds: Difference between revisions
Jump to navigation
Jump to search
| (9 intermediate revisions by the same user not shown) | |||
| Line 4: | Line 4: | ||
=TODEPLETE= | =TODEPLETE= | ||
{{Internal|Gradle Multi-Project Builds TODEPLETE|Gradle Multi-Project Builds TODEPLETE}} | {{Internal|Gradle Multi-Project Builds TODEPLETE|Gradle Multi-Project Builds TODEPLETE}} | ||
=Overview= | |||
Sub-projects can depend on each other in the context of a multi-project build. | |||
=Inter-Project Dependencies= | |||
Projects that are part of the same multi-project build may be related to each other via two kind of dependencies: [[#Project_Dependencies|project dependencies]] and [[#Task_Dependencies|task dependencies]]. | |||
==Project Dependencies== | |||
{{External|https://docs.gradle.org/current/userguide/declaring_dependencies.html#sub:project_dependencies}} | |||
Projects (modules) can define dependencies between each other to reuse code. A project dependency is declared with the following syntax in [[build.gradle]]: | |||
<syntaxhighlight lang='groovy'> | |||
dependencies { | |||
implementation project(':shared') | |||
} | |||
</syntaxhighlight> | |||
==Task Dependencies== | |||
{{Internal|Gradle_Task_Dependencies_and_Ordering#Overview|Task Dependencies}} | |||
Latest revision as of 01:33, 22 October 2020
Internal
TODEPLETE
Overview
Sub-projects can depend on each other in the context of a multi-project build.
Inter-Project Dependencies
Projects that are part of the same multi-project build may be related to each other via two kind of dependencies: project dependencies and task dependencies.
Project Dependencies
Projects (modules) can define dependencies between each other to reuse code. A project dependency is declared with the following syntax in build.gradle:
dependencies {
implementation project(':shared')
}