This page is a guide for the below warning:
2017-01-15 22:02:46.033127 Warning MODULMSG ; Job execution end of comment '\*\/' not found 0 ; 0 0 0 [Module name] 0 0
2017-01-15 22:02:46.033127 Warning MODULMSG ; Job execution File skipped : K:\CAST\CASTMS\Deploy\\test-staticresources\bower_components\angular\angular.min.js
Release | Yes/No |
|---|---|
| 8.3.x |  |
| 8.2.x | |
| 8.1.x | |
| 8.0.x | |
| 7.3.x | |
RDBMS | Yes/No |
|---|---|
| Oracle Server | |
| Microsoft SQL Server | |
| CSS3 | |
| CSS2 | |
Below is the step-by-step scenario leading to the problem:
- Install HTML5 and JS extension from server manager
- Package and deliver the source code.
- Accept the delivery and run the analysis.
The impact of the problem on the analysis or the dashboard is : There will be no impact
The scenario here is that the files are ignored by the UA analyzer and it raises a warning as shown above but will subsequently be analyzed by the extension.
This can be seen when we see the files parsed by the extension.
Details of the same can be found below.
First the underlying Universal Analyzer considers all the files and raises a warning whenever it encounters what it considers a parsing error (that is why you see those warnings 'comment not found').
Find the content of analysis log below:2017-01-15 22:02:23.678040 Warning MODULMSG ; Job execution end of comment '\*\/' not found 0 ; 0 0 0 [Module name] 0 0 2017-01-15 22:02:23.678040 Warning MODULMSG ; Job execution File skipped : K:\CAST\CASTMS\Deploy\Test_source\Ref\auto-refi2-staticresources\testing\inflow.js
Then the HTML5 analyzer filters out the 3rd-party files (at least those which are recognized as part of a known 3rd-party framework)
and does a light-parsing then a full-parsing of the others like inflow.js. Find the content of analysis log below in which the file has been parsed by the HTML extension2017-01-15 22:03:23.614008 Information MODULMSG ; Job execution [com.castsoftware.html5] Light parsing of file K:\CAST\CASTMS\Deploy\Test_source\Ref\auto-refi2-staticresources\testing\inflow.js
If your case does not match with the one listed above then contact CAST Technical Support with Relevant Input.
Impact of the solution on the analysis or the dashboard is : No Impact
