Release Notes - 1.0
1.0.3
Other Updates
| Details |
|---|
| To help clarify why some files were not analyzed (in reports provided by CAST Console), a change has been made to ensure that generated code files (which are never analyzed) are now explicitly marked as generated code and will therefore be actively excluded from analysis by a specific exclusion rule for generated code. This means that CAST Console will be able to report that the generated code files were specifically excluded by a rule. In previous releases, generated code was simply ignored and therefore CAST Console was not able to give a reason why the code was not analyzed. Note that this change requires AIP Core ≥ 8.3.52. |
1.0.2
Resolved Issues
| Customer Ticket Id | Details |
|---|---|
| 41458 | Fixes an issue where the “Accept Version” step fails with the error: “The packaging in the Delivery has not been fully completed.” |
1.0.1
Resolved Issues
| Customer Ticket Id | Details |
|---|---|
| 38586 | Fixes an issue where the extraction of maven artifacts failed with the warning “cast.dmt.discover.jee.maven.missingPomParent” because the maven parent artifact required by a maven artifact was missing. |
| 39358 | Fixes the Discovery Error - “java.util.regex.PatternSyntaxException:Illegal/unsupported” escape sequence near index 52. |
1.0.0
Resolved Issues
| Customer Ticket Id | Details |
|---|---|
| 36548 | Fixed an issue where the Analysis Unit was not created and the error “the packaging type is - ${project.packaging}” was seen in the log. |
| 36302 | Fixed an issue where the automatic extraction of Maven dependencies was incorrectly fetching the wrong .jar file version despite the correct version being defined in the dependencies file. |
Other Updates
| Details |
|---|
| Fixed a fatal error in the JEE Analyzer: “Invalid Web Application Root Path” when the path contains unresolved Maven properties. |
| Fixed an issue where Maven projects containing ejb-jar.xml files but no Java source code are not transformed into Analysis Units. |