# SonarQube for IDE creates .sonar/spring-context-model.json in every analyzed module in Eclipse

**URL:** <https://community.sonarsource.com/t/sonarqube-for-ide-creates-sonar-spring-context-model-json-in-every-analyzed-module-in-eclipse/190547>\
**Category:** Eclipse\
**Tags:** connected\_mode, java\
**Created:** [October 27, 2026, 11:08am UTC](https://community.sonarsource.com/t/sonarqube-for-ide-creates-sonar-spring-context-model-json-in-every-analyzed-module-in-eclipse/190547 "2026-10-27T11:08:43Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![lrozenblyum](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/lrozenblyum/32/11922_2.png) [@lrozenblyum](https://community.sonarsource.com/u/lrozenblyum)\
**Post date:** [October 27, 2026, 11:08am UTC](https://community.sonarsource.com/t/sonarqube-for-ide-creates-sonar-spring-context-model-json-in-every-analyzed-module-in-eclipse/190547/1 "2026-10-27T11:08:43Z")

</div>

- Operating system: Windows 10 Pro (10.0.19045)
- IDE name and version: Eclipse IDE 2026-06
- SonarQube for Eclipse plugin version: 13.2.0.84960
- Programming language you’re coding in: Java (multi-module Maven project, Spring Boot)
- Is connected mode used: Yes
- SonarQube Cloud, SonarQube Server, or SonarQube Community Build? (if one of the latter two, which version?): SonarQube Cloud (EU)

Since around 2026-10-23, a new folder appears in each module of our working copy as soon as a file in it is analyzed:

`<module>/.sonar/spring-context-model.json`

Our repositories have never needed an ignore rule for `.sonar`, so these show up as many new untracked files that every developer has to clean up or ignore. Deleting them does not help, they come back with the next analysis.

We could not find any mention of these files in the SonarQube for IDE documentation, the analyzer documentation or the release notes.

Questions:

1. Is creating this folder in the project directories intended?

2. If so, could it be documented, ideally with a recommended ignore rule, or written outside the project directories (for example into the IDE’s own storage)?

---

<div class="post-metadata">

**Author:** ![Dick\_Dijk](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/dick_dijk/32/19572_2.png) [@Dick\_Dijk](https://community.sonarsource.com/u/Dick_Dijk)\
**Post date:** [October 27, 2026, 6:16pm UTC](https://community.sonarsource.com/t/sonarqube-for-ide-creates-sonar-spring-context-model-json-in-every-analyzed-module-in-eclipse/190547/5 "2026-10-27T18:16:49Z")

</div>

Same problem in IntelliJ

---

<div class="post-metadata">

**Author:** ![nicolas.quinquenel](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/nicolas.quinquenel/32/40740_2.png) [@nicolas.quinquenel](https://community.sonarsource.com/u/nicolas.quinquenel)\
**Post date:** [October 27, 2026, 6:34pm UTC](https://community.sonarsource.com/t/sonarqube-for-ide-creates-sonar-spring-context-model-json-in-every-analyzed-module-in-eclipse/190547/6 "2026-10-27T18:34:56Z")

</div>

Hello, thanks for raising the issue!

This is an unwanted change from our Sonar Java analyzer, recently shipped on SonarQube Cloud. We are working on a fix and will let you know ASAP!

For now, you can either ignore this file/folder, or avoid using connected mode with SonarQube Cloud.

---

<div class="post-metadata">

**Author:** ![aurelien.coet](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/aurelien.coet/32/76605_2.png) [@aurelien.coet](https://community.sonarsource.com/u/aurelien.coet)\
**Post date:** [October 28, 2026, 2:09pm UTC](https://community.sonarsource.com/t/sonarqube-for-ide-creates-sonar-spring-context-model-json-in-every-analyzed-module-in-eclipse/190547/10 "2026-10-28T14:09:11Z")

</div>

Hello @lrozenblyum,

Looking at the files you mention in your message, I was surprised to see that you report getting `.sonar/spring-context-model.json` files in each module of your project. I would have expected it to only appear once, at the project’s root. I was thus wondering if you could share more about your Maven configuration for the analysis ?

Best regards,  
Aurélien

---

<div class="post-metadata">

**Author:** ![lrozenblyum](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/lrozenblyum/32/11922_2.png) [@lrozenblyum](https://community.sonarsource.com/u/lrozenblyum)\
**Post date:** [October 28, 2026, 3:22pm UTC](https://community.sonarsource.com/t/sonarqube-for-ide-creates-sonar-spring-context-model-json-in-every-analyzed-module-in-eclipse/190547/11 "2026-10-28T15:22:24Z")

</div>

Hello @aurelien.coet

Thanks for looking into it. Here are the details of our setup:

- The aggregator POM is not at the repository root but in a sibling folder `Parent/`, next to the modules, and it references them as `<module>../ModuleA</module>`, `<module>../ModuleB</module>`, … So no module is nested under the aggregator, and the repository root itself has no `pom.xml`.
- In Eclipse, m2e imports every Maven module as its own Eclipse project. There is no Eclipse project for the repository root.
- Each of these Eclipse projects (about 250) is bound in connected mode to the same SonarQube Cloud project.
- So far, .sonar/spring-context-model.json has appeared in 12 modules. In one more module, the `.sonar` folder was created but stayed empty.
- The analysis on SonarQube Cloud runs in CI with `sonar-maven-plugin` 5.6.0.6792 from the aggregator POM (`mvn ... sonar-maven-plugin:sonar -f Parent/pom.xml`).
