# Build-wrapper-dump.json does not match analyzer 6.20.4.45706 version

**URL:** <https://community.sonarsource.com/t/build-wrapper-dump-json-does-not-match-analyzer-6-20-4-45706-version/62245>\
**Category:** SonarQube Server / Community Build\
**Tags:** cfamily, sonarqube, scanner\
**Created:** [April 26, 2022, 1:49pm UTC](https://community.sonarsource.com/t/build-wrapper-dump-json-does-not-match-analyzer-6-20-4-45706-version/62245 "2022-04-26T13:49:56Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![Bree](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/bree/32/31530_2.png) [@Bree](https://community.sonarsource.com/u/Bree)\
**Post date:** [April 28, 2022, 6:25am UTC](https://community.sonarsource.com/t/build-wrapper-dump-json-does-not-match-analyzer-6-20-4-45706-version/62245/7 "2022-04-28T06:25:00Z")

</div>

Nope, the actual file names are fine 😉

The resolving of the includes in c++ causes this issue.

Something like this

```auto
#include "detailtextdlg.h "

```

Will be resolved to a path with trailing whitespaces, which causes the error in `WindowsPathParser`.

The Issue is solved by executing regex search and replace of all include statements that contained a trailing space, for example, `#include "detailtextdlg.h " ` to `#include "detailtextdlg.h"`

i.e: our builds are green again 😉

---

_[View the full topic](https://community.sonarsource.com/t/build-wrapper-dump-json-does-not-match-analyzer-6-20-4-45706-version/62245)._