Menu

Why Sanity4J cannot find sources for analysis

Help
Mei Ding
2011-06-09
2013-05-28
  • Mei Ding

    Mei Ding - 2011-06-09

    I have configured Sanity4J-1.0.2 in Maven 3 build, here is the POM reporting plugin for Sanity4j:
    <reporting>
                   <plugins>
                           …
    <plugin>
           <groupId>org.codehaus.mojo</groupId>
            <artifactId>cobertura-maven-plugin</artifactId>
            <version>2.4</version>
             <configuration>
                    <formats>
    <format>html</format>
    <format>xml</format>
                    </formats>
                </configuration>
          </plugin>
                                  <plugin>
            <groupId>net.sf.sanity4j</groupId>
            <artifactId>sanity4j</artifactId>
            <version>1.0.2</version>               
            <configuration>
            <productsDir>C:/sanity4j-1.0.2/tools</productsDir>
            </configuration>
          </plugin>

                 </plugins>
    </reporting>

    The project structure is set all using Maven project default.

    Cobertura test coverage report is generated fine, however no Sanity4J report is generated (In target/site/sanity4j directory, only one empty index.html). In Maven process console, I have had the lines of system message:
                 Generating "Sanity4J Report" report    -- sanity4j:1.0.2
                 petmotel core java module contains no java source files. Skipping analysis.
    (while "petmotel core java module " is the Maven project name in POM.xml)

    Why Sanity4J says the project containing no source files, as the Java source files are sitting in 'src/main/java' and 'src/test/java' directory? I even tried adding
              <sources>
                         <source>src/main/java</source>
                          <source>src/test/java</source>
                 </sources>
    and
                 <sources>
                         <sourcePath>src/main/java</sourcePath>
                          <sourcePath>src/test/java</sourcePath>
                 </sources>
    but had the exact same results.

     
  • Yiannis Paschalidis

    There seems to have been a bug introduced in the Maven changes for 1.0.2. We're working on a fix and hope to have 1.0.3 out soon.