This article includes a list the new features and bug fixes that are included in Lucent Sky AVM version 1810, as well as known issues of this release.
For more information about this release, visit the blog post Lucent Sky AVM version 1810 released.
Updates in Lucent Sky AVM version 1810
-
Architectural improvements - improvements on the I/O stack for compilation and analysis.
-
Report - the reporting engine for HTML and PDF reports were rewritten to improve report generation performance.
-
OpenJDK migration - the included Oracle JDKs have been replaced by their Open JDK counterparts. In the unlikely scenario that your application requires Oracle JDKs, contact Lucent Sky support regarding setting up an alternative JDK for Lucent Sky AVM.
-
Bug fix - Several UI bug fixes and other cosmetic improvements were included in version 1810.
List of fixes included in Lucent Sky AVM version 1810
External classpaths defined in build.xml are ignored by Ant
If an application has external classpaths defined in its build.xml, they are ignored by Ant. This issue is caused by incorrect behavior by the new Ant compiler. This issue first appeared in Lucent Sky AVM version 1810.
This issue has been resolved in Lucent Sky AVM version 1810.
The Analysis Engines field of some applications does not appear or is empty in the Web UI and reports
This is caused by a data migration bug when updating to Lucent Sky AVM version 1810. This only affects a very small percentage of applications scanned with earlier version of Lucent Sky AVM that use an unique set of scan arguments. This issue first appeared in Lucent Sky AVM version 1810.
This issue has been resolved in Lucent Sky AVM version 1810.
Known issues of Lucent Sky AVM version 1810
Scanning .NET web site failed with result code -49999990
When scanning a .NET web site, the scan failed with the result code -49999990. Additionally, the compilation logs include the following:
An unexpected error has occurred. The correlation ID is c8ebd46a-f8dc-43b8-a94c-dd9c046c5b1c.
This issue is presents in Lucent Sky AVM version 1809 and 1810. It is expected to be resolved in Lucent Sky AVM version 1811. A workaround for this issue, is to create a dummy .csproj file (for example, foo.csproj) in the root of the web site.