# Plugin java-test-fixtures cannot resolve Spring Boot starter dependencies

**URL:** <https://discuss.gradle.org/t/plugin-java-test-fixtures-cannot-resolve-spring-boot-starter-dependencies/44965>\
**Category:** Help/Discuss\
**Created:** [February 22, 2023, 11:15am UTC](https://discuss.gradle.org/t/plugin-java-test-fixtures-cannot-resolve-spring-boot-starter-dependencies/44965 "2023-02-22T11:15:53Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![crlik](https://avatars.discourse-cdn.com/v4/letter/c/49beb7/32.png) [@crlik](https://discuss.gradle.org/u/crlik)\
**Post date:** [February 22, 2023, 11:15am UTC](https://discuss.gradle.org/t/plugin-java-test-fixtures-cannot-resolve-spring-boot-starter-dependencies/44965/1 "2023-02-22T11:15:54Z")

</div>

Hi,  
we have rather complicated structure of our modules but I tried to add java-test-fixtures to one of my Gradle subprojects but build suddenly started to fail with:

```gradle
* What went wrong:
Execution failed for task ':modules:transform:compileTestFixturesJava'.
> Could not resolve all files for configuration ':modules:transform:testFixturesCompileClasspath'.
   > Could not find org.springframework.boot:spring-boot-starter-actuator:.
     Required by:
         project :modules:transform
   > Could not find org.springframework.boot:spring-boot-starter-web:.
     Required by:
         project :modules:transform

```

(and some others). I only added `id "java-test-fixtures"` line into the script. And we use Spring Boot in our project. But I am super puzzled why it cannot be resolved now.

Does fixture plugin somehow have troubles with Spring Boot dependency plugin or something?  
 → We are using Gradle 7.5.1

Thanks for pointing me into any direction.

---

<div class="post-metadata">

**Author:** ![Vampire](https://sea1.discourse-cdn.com/gradle/user_avatar/discuss.gradle.org/vampire/32/9082_2.png) [@Vampire](https://discuss.gradle.org/u/Vampire)\
**Post date:** [February 22, 2023, 1:05pm UTC](https://discuss.gradle.org/t/plugin-java-test-fixtures-cannot-resolve-spring-boot-starter-dependencies/44965/2 "2023-02-22T13:05:05Z")

</div>

Try using the built-in BOM support instead.  
The Spring dependency management plugin is a relict from times when Gradle had no built-in BOM support and even its maintainer recommends to use the built-in functionality instead.

---

<div class="post-metadata">

**Author:** ![crlik](https://avatars.discourse-cdn.com/v4/letter/c/49beb7/32.png) [@crlik](https://discuss.gradle.org/u/crlik)\
**Post date:** [February 22, 2023, 1:19pm UTC](https://discuss.gradle.org/t/plugin-java-test-fixtures-cannot-resolve-spring-boot-starter-dependencies/44965/3 "2023-02-22T13:19:03Z")

</div>

I will happily try. I want to switch to version catalog anyway. Thank you very much.

But I have to admit I am quite confused right now. There are two plugins:

- org.springframework.boot
- io.spring.dependency-management

I am not sure which one should I remove. Or maybe there is a blog post or a page explained how to replace Spring dependency management plugin?

---

<div class="post-metadata">

**Author:** ![Vampire](https://sea1.discourse-cdn.com/gradle/user_avatar/discuss.gradle.org/vampire/32/9082_2.png) [@Vampire](https://discuss.gradle.org/u/Vampire)\
**Post date:** [February 22, 2023, 1:56pm UTC](https://discuss.gradle.org/t/plugin-java-test-fixtures-cannot-resolve-spring-boot-starter-dependencies/44965/4 "2023-02-22T13:56:58Z")

</div>

You still need `org.springframework.boot`.  
You want to remove the dependency management one and instead use a `platform(...)` dependency as documented in the spring boot documentation.

---

<div class="post-metadata">

**Author:** ![crlik](https://avatars.discourse-cdn.com/v4/letter/c/49beb7/32.png) [@crlik](https://discuss.gradle.org/u/crlik)\
**Post date:** [February 23, 2023, 6:30am UTC](https://discuss.gradle.org/t/plugin-java-test-fixtures-cannot-resolve-spring-boot-starter-dependencies/44965/5 "2023-02-23T06:30:25Z")

</div>

Oh, yes. I really found some weird mix of features/plugins and some of them are deprecated as well. After removing the plugin and some strange functions it works in my module.

Thank you very much Björn!