1.0.25

Updates

Stability improvements

• In previous releases, if your source code included multiple jars containing the same class, the order of resolution of these classes was not stable from one analysis to another. This improvement corrects this issue and ensures that the order always stays the same in successive analyses. The benefits of this stability improvement will be visible in subsequent re-analyses where the order of resolution will remain stable.
• Better handling of exceptions that were causing the entire analysis to stop in previous releases of the extension:
  • Access violation (null pointer, ...)
  • AMT: invalid null pointer for wrapped instance, invalid category <category_name> used in type <type_name>
  • MetaModel exception, std::exception
  • InferenceEngine exception
  • Fixed stability issues during CAST Script processing

Performance improvements

• Significant performance improvement (from hours to minutes) during the "Generating JSP implementation classes" phase when an application has >5000 JSP pages.

Link improvements

• Updated resolution for links to unresolved methods
  • Before this release, when creating links between methods, the analyzer attempts to find exact matches for the methods.
  • From this release onwards, if no exact match is found, the analyzer uses heuristics to filter and detect partial matches, and then creates links for all such matches.
  • This makes the analyzer more resistant from one analysis to another when adding missing code or jars.
• Fixed missing Access exec links between java methods due to generated Lombok methods using @Getter annotation.
• Fixed some incorrect FIRE links when there is no inheritance between the abstract method and the implementation method.
• Fixed some incorrect USE links from Java methods to JPA entity properties.
• Changed direction of RELY ON link between JPA Entity and Java Field objects.

Rule improvements

Resolved issues

Below table lists the bugs fixed in the current release.