Analysis of multi-module Maven project

SonarQube
,
1

my Maven project Structure is like below Module1 and Module 2 contains spark scala and unix wrapper script, Module 3 contains Shell Scripts/Python /plsql codes.

project
    Module -1
	    Submodule 1
		      Submodule-1-version-1/src/main
			  Submodule-1-version-2/src/main
	    Submodule 2
		      Submodule-2-version-1/src/main
			  Submodule-2-version-2/src/main
    Module -2
	    Module -1
	    Submodule 1
		      Submodule-1-version-1/src/main
			  Submodule-1-version-2/src/main
	    Submodule 2
		      Submodule-2-version-1/src/main
			  Submodule-2-version-2/src/main
    Module -3
	     Module -1
	    Submodule 1
		      Submodule-1-version-1/Script
			   Submodule-1-version-2/Script
	    Submodule 2
		      Submodule-2-version-1/Script
			  Submodule-2-version-2/Script

every execution of mvn sonar:sonar failed with error Saying Script directory not exists in module-1 or module 2.

How to setup module wise sonar.sources so that sonar will pick my all java/scala/python/shell and plsql codes

Below are the sonar property in POM

<encoding>UTF-8</encoding>
        <scoverage.highlighting>true</scoverage.highlighting>
        <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
        <project.reporting.outputEncoding>UTF-8</project.reporting.outputEncoding>
        <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
        <!-- Sonar setup -->
        <!--suppress UnresolvedMavenProperty -->
        <sonar.host.url>${env.SONAR_URL}</sonar.host.url>
        <!--suppress UnresolvedMavenProperty -->
        <sonar.login>${env.SONAR_TOKEN}</sonar.login>
        <!--suppress UnresolvedMavenProperty -->
        <sonar.projectKey>${env.SONAR_PROJECT_KEY}</sonar.projectKey>
        <sonar.moduleKey>${project.artifactId}</sonar.moduleKey>
        <sonar.core.codeCoveragePlugin>scoverage</sonar.core.codeCoveragePlugin>
        <sonar.scala.version>${scala.version}</sonar.scala.version>
        <sonar.scala.coverage.reportPaths>target/scoverage.xml</sonar.scala.coverage.reportPaths>
        <sonar.coverage.jacoco.xmlReportPaths>target/site/jacoco/jacoco.xml</sonar.coverage.jacoco.xmlReportPaths>
        <sonar.sources>src/main/,Scripts</sonar.sources>
        <sonar.java.binaries>.</sonar.java.binaries>
        <sonar.tests>src/test</sonar.tests>
        <sonar.inclusion>**/*.py,**/*.sh,**/*.ksh,**/*.java,**/*.scala,**/*.xml</sonar.inclusion>
        <sonar.sourceEncoding>UTF-8</sonar.sourceEncoding>
2

Hi,

Welcome to the community!

I’ve moved your post to a new thread, since the topic you posted it in had been dormant for nearly 3 years.

Yours is definitely a case of “less is more”. For Maven analysis, most of those properties you’ve specified manually are automatically provided by Maven. The fact that you’ve overridden those default values is probably the problem.

I would try it with this scaled-down set:

<encoding>UTF-8</encoding>
        <scoverage.highlighting>true</scoverage.highlighting>
        <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
        <project.reporting.outputEncoding>UTF-8</project.reporting.outputEncoding>
        <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
        <!-- Sonar setup -->
        <sonar.host.url>${env.SONAR_URL}</sonar.host.url>
        <sonar.login>${env.SONAR_TOKEN}</sonar.login>

 
HTH,
Ann

3

Must-share information (formatted with Markdown):
Sonar Developer edition

my Maven project Structure is like below Module1 and Module 2 contains spark scala and unix wrapper script, Module 3 contains Shell Scripts/Python /plsql codes.

project
Module -1
-----Submodule 1
--------Submodule-1-version-1/src/main
--------Submodule-1-version-2/src/main
-----Submodule 2
--------Submodule-2-version-1/src/main
--------Submodule-2-version-2/src/main
Module -2
-----Module -1
-----Submodule 1
--------Submodule-1-version-1/src/main
--------Submodule-1-version-2/src/main
-----Module -2
-----Submodule 2
--------Submodule-2-version-1/src/main
--------Submodule-2-version-2/src/main
Module -3
-----Module -3
-----Submodule 1
--------Submodule-1-version-1/Script
--------Submodule-1-version-2/Script
-----Submodule 2
--------Submodule-2-version-1/Script
--------Submodule-2-version-2/Script

every execution of mvn sonar:sonar failed with error Saying Script directory not exists in module-1 or module 2.

How to setup module wise sonar.sources so that sonar will pick my all java/scala/python/shell and plsql codes

Below are the sonar property in POM
UTF-8
<scoverage.highlighting>true</scoverage.highlighting>
<project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
<project.reporting.outputEncoding>UTF-8</project.reporting.outputEncoding>
<project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>

<sonar.host.url>${env.SONAR_URL}</sonar.host.url>

<sonar.login>${env.SONAR_TOKEN}</sonar.login>

<sonar.projectKey>${env.SONAR_PROJECT_KEY}</sonar.projectKey>
<sonar.moduleKey>${project.artifactId}</sonar.moduleKey>
<sonar.core.codeCoveragePlugin>scoverage</sonar.core.codeCoveragePlugin>
<sonar.scala.version>${scala.version}</sonar.scala.version>
<sonar.scala.coverage.reportPaths>target/scoverage.xml</sonar.scala.coverage.reportPaths>
<sonar.coverage.jacoco.xmlReportPaths>target/site/jacoco/jacoco.xml</sonar.coverage.jacoco.xmlReportPaths>
<sonar.sources>src/main/,Scripts</sonar.sources>
<sonar.java.binaries>.</sonar.java.binaries>
<sonar.tests>src/test</sonar.tests>
<sonar.inclusion>/.py,/.sh,**/.ksh,/.java,/.scala,**/.xml</sonar.inclusion>
<sonar.sourceEncoding>UTF-8</sonar.sourceEncoding>

4

Hi @Manish_Kumar_Gupta,

You created nearly identical topics only minutes apart. Please don’t do that. There is a limited bandwidth on the “answerer” side in this community. Double-posting means you may take up twice the bandwidth for one question.

I’ve combined your here.

 
Ann

5

Corrected POM.xml as per your inputs but still plsql/python/unix scripts are not included from any module

there are 2 type of modules (Maven and Non-Maven)

Maven Module-1 (Java /Scala Maven Framework)
-conf (Used to keep internal module configurations)
-script (Unix and Python wrapper which will execute jar)
-src/main (Source code and Test)

NON Maven Module-2 (Unix or Python Scripts)
-script (Unix and Python wrapper )

6

Hi,

Your initial post mentioned an error. From your followup, I guess you don’t get the error any more and you’re trying to move on to a different problem? If so, please create a new thread for this new problem. If not, please post your full analysis log.

 
Ann

7

its not different , issue remains same, python/shell script are not picked up for maven scanner

8

Hi,

Your initial post reported an error. To me an error means analysis stops. In which case no files are analyzed. Does analysis complete?

And please post your full analysis log.

 
Ann