# Launching maven plugin separately **URL:** \ **Category:** SonarQube Cloud\ **Tags:** java, sonarqube-cloud, scanner\ **Created:** [March 12, 2025, 10:53am UTC](https://community.sonarsource.com/t/launching-maven-plugin-separately/136672 "2025-03-12T10:53:26Z")\ **Posts on this page:** 1\ **Showing post:** 3
**Author:** ![sbernard](https://avatars.discourse-cdn.com/v4/letter/s/58f4c7/32.png) [@sbernard](https://community.sonarsource.com/u/sbernard)\ **Post date:** [March 13, 2025, 2:52pm UTC](https://community.sonarsource.com/t/launching-maven-plugin-separately/136672/3 "2025-03-13T14:52:16Z")
> [@sbernard](#): > > this allow us to continue to execute some goals even if one critical one failed. Sorry that was a typo. I wanted to write _“if **not** critical one failed”_. And this is not the only one reason we do that so even the first was strange to you maybe the second make more sense ? _“this allow us to generate custom private comment for each goals.”_ If you want to better understand our use case, take a look at code I share. I also explain some example in my previous comment… Ideally I understand I should do a full build ([even tests](https://community.sonarsource.com/t/on-maven-builds-can-sonar-sonar-be-run-in-parallel/80726/2)) before sonar goal. What concretely I lost if I don’t do that. If I can not follow that recommendation will I have worst result than automatic mode ? 🤷 --- _[View the full topic](https://community.sonarsource.com/t/launching-maven-plugin-separately/136672)._