# Resolving circular included builds

**URL:** <https://discuss.gradle.org/t/resolving-circular-included-builds/45620>\
**Category:** Help/Discuss\
**Created:** [May 17, 2023, 9:14pm UTC](https://discuss.gradle.org/t/resolving-circular-included-builds/45620 "2023-05-17T21:14:27Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![kelvSYC](https://avatars.discourse-cdn.com/v4/letter/k/919ad9/32.png) [@kelvSYC](https://discuss.gradle.org/u/kelvSYC)\
**Post date:** [May 17, 2023, 9:14pm UTC](https://discuss.gradle.org/t/resolving-circular-included-builds/45620/1 "2023-05-17T21:14:27Z")

</div>

Suppose in my Gradle project I have two included builds, `A` and `B`. In `A/settings.gradle.kts` I have

```gradle
includeBuild("../B")

```

and likewise I have in `B/settings.gradle.kts` I have

```gradle
includeBuild("../A")

```

Of course, this would obviously cause things to fail to build, but there are likely use cases where you might see this happen (for example, if `A` was a convention plugin that sets a project’s version, and `B` was a convention plugin that configures publishing settings).

What’s the best way to resolve such circular inclusions?