Hudson understands the format of compiler Codescanner. When this option is configured, Hudson can provide useful information about the compiler warnings, such as historical result trend, web UI for viewing analysis reports, and so on. To use this feature, configure your compiler to write all warnings to the log file.

Ant Configuration

To get the Ant javac task to include compiler warnings in the build output you must (a) avoid specifying nowarn="on" ("off" is the default) and (b) include the -Xlint compiler argument (or some variant thereof). Example:

    
<javac deprecation="true" destdir="classes">
  <compilerarg value="-Xlint"/>
</javac>
    
  

Maven Configuration

If you are using maven to compile your sources, place the following snippet into your pom.xml to enable the compiler Codescanner.

    

<plugins>
  [...]
  <plugin>
    <groupId>org.apache.maven.plugins</groupId>
    <artifactId>maven-compiler-plugin</artifactId>
    <configuration>
      <showDeprecation>true</showDeprecation>
      <showWarnings>true</showWarnings>
    </configuration>
  </plugin>
[...]

</plugins>
    
  

Oracle Invalids Configuration

In order to visualize the invalids of your Oracle database you need to copy the output of the following SQL statement to the console log.

    
SELECT   dao.owner, dao.object_name, dao.object_type, dao.status, dae.line, dae.position, dae.text
    FROM dba_objects dao, dba_errors dae
   WHERE dao.status = 'INVALID'
     AND dao.owner = dae.owner(+)
     AND dao.object_name = dae.name(+)
     AND dao.object_type = dae.type(+)
ORDER BY object_type, object_name;