I understand that this may very well not be the optimal structure for this project. My question is mostly geared towards understanding if it’s possible for the Sonar scan to handle this project in its current state. If it’s absolutely not possible, then we can investigate alternative project structuring, or any other suggestions.

Ideally we’d like to run scans against both sub-modules. mvn sonar:sonar is invoked in our CI pipeline in the application/spring directory. The reason for scanning the project via the Maven Sonar plugin is that this project uses a templated CI pipeline, and that templated CI pipeline invokes one build system (based on developer specification in a pipeline configuration file) to download dependencies, compile, test, package and publish. So we use Maven but also register custom npm tasks into the build lifecycle using the exec-maven-plugin. I realize this might also be an area of opportunity, but it’s the best solution we’ve devised thus far to fit into our templated CI pipeline solution.