.github/                                    @gradle/bt-developer-productivity @gradle/bt-support # This might need to be more finegrained in the future
/build-logic/                               @gradle/bt-developer-productivity
/build-logic-commons/                       @gradle/bt-developer-productivity
/build-logic-settings/                      @gradle/bt-developer-productivity
/build.gradle*                              @gradle/bt-developer-productivity

We want to apply a set of code quality checking rules to both types of projects and configure some aspects specific to each type.


== Organizing build logic

The use case can be modelled by layering three separate plugins:

====
[.multi-language-sample]
=====
.Build logic layout
[source, kotlin]
----
├── convention-plugins
│   ├── build.gradle.kts
│   ├── settings.gradle.kts
│   ├── src
│   │   ├── main

We want to apply a set of code quality checking rules to both types of projects and configure some aspects specific to each type.


== Organizing build logic

The use case can be modelled by layering three separate plugins:

====
[.multi-language-sample]
=====
.Build logic layout
[source, kotlin]
----
├── convention-plugins
│   ├── build.gradle.kts
│   ├── settings.gradle.kts
│   ├── src
│   │   ├── main

Please be aware that these options disable the validation that makes execution parallel- and caching-safe when isolated projects is enabled,
so you may see some unexpected behaviour when using them.

== Build logic constraints

Isolated projects prevents build logic from accessing the state of another project. This includes:

* Using most methods on the `Project` type. A small number of methods that return immutable information about the project are allowed:

apiVersion: release-notes/v2
kind: bug-fix
area: traffic-management
issue:
  - 50596

releaseNotes:
- |

rootProject.name = 'logic-during-configuration-do'...

== Organizing build logic

From the use case above, we have identified that we have two types of projects - generic Java projects and public libraries.
We can model this use case by layering two separate plugins that each define the type of project that applies them:

====
[.multi-language-sample]
=====
.Build logic layout
[source, kotlin]
----
├── buildSrc
│   ├── build.gradle.kts

plugins {
    id("gradlebuild.build-logic.kotlin-dsl-gradle-plugin")
}

description = "Provides a plugin to minify and correct metadata for dependencies used by Gradle"

dependencies {
    implementation("gradlebuild:basics")
    implementation("com.google.code.gson:gson")

5. **Return type **of original call
6. **The receiver** of original call
7. **Parameters** of original call
8. **Logic** with call interception logic or logic that translates the new type to the old type

This JavaCompileInterceptorsDeclaration will then generate interceptors in **org.gradle.internal.classpath.generated** package.

For Java:
```java

// tag::include-subprojects[]
include("app")
include("data-model")
//include("database-logic")
// end::include-subprojects[]