Page tree
Skip to end of metadata
Go to start of metadata

Packaging and delivery

Note that the AngularJS extension does not contain any CAST Delivery Manager Tool discoverers or extractors, therefore, no "AngularJS" projects will be detected. However, the Web Files Discoverer extension will be automatically installed (it is a "shipped" extension which means it is delivered with AIP Core) and will automatically detect projects as HTML5 if specific files are delivered, therefore ensuring that Analysis Units are created for your source code.

Using AIP Console

Using CAST Management Studio

 Click here to expand...
  • create a new Version
  • create a new Package for your AngularJS source code using the Files on your file system option:

  • Define the root folder of your Application source code:

  • Run the Package action
  • Before delivering the source code, check the packaging results:
Without the Web Files Discover

If you are not using the Web Files Discoverer, the following will occur:

  • the CAST Delivery Manager Tool will not find any "projects" related to the AngularJS application source code - this is the expected behaviour. However, if your AngularJS related source code is part of a larger application (for example a JEE application), then other projects may be found during the package action (click to enlarge):

With the Web Files Discoverer

If you are using the Web Files Discoverer, the following will occur:

  • the CAST Delivery Manager Tool will automatically detect "HTML5 file projects" (see Web Files Discoverer for more technical information about how the discoverer works) related to the AngularJS application source code. In addition, if your AngularJS related source code is part of a larger application (for example a JEE application), then other projects may also be found during the package action (click to enlarge):

  • Deliver the version.

Analyzing

Using AIP Console

AIP Console exposes the technology configuration options once a version has been accepted/imported, or an analysis has been run. Click Universal Technology (3) in the Config (1) > Analysis (2) tab to display the available options for your AngularJS source code:

Then choose the relevant Analysis Unit (1) to view the configuration:

Using the CAST Management Studio

 Click here to expand...

Accept and deploy the Version in the CAST Management Studio.

Without the Web Files Discover

If you are not using the Web Files Discoverer, the following will occur:

  • No Analysis Units will be created automatically relating to the AngularJS source code - this is the expected behaviour. However, if your AngularJS related source code is part of a larger application (for example a JEE application), then other Analysis Units may be created automatically:

  • In the Current Version tab, add a new Analysis Unit specifically for your AngularJS source code, selecting the Add new Universal Analysis Unit option:

  • Edit the new Analysis Unit and configure in the Source Settings tab:
    • a name for the Analysis Unit
    • ensure you tick the HTML5/JavaScript option (the AngularJS extension depends on the HTML5 and JavaScript extension - and therefore the Universal Analyzer language for the AngularJS extension is set as HTML5/JavaScript)
    • define the location of the deployed AngularJS source code (the CAST Management Studio will locate this automatically in the Deployment folder):

  • Run a test analysis on the Analysis Unit before you generate a new snapshot.
With the Web Files Discoverer

If you are using the Web Files Discoverer, the following will occur:

  • "HTML5" Analysis Units will be created automatically (see Web Files Discoverer for more technical information about how the discoverer works) related to the AngularJS application source code. In addition, if your AngularJS related source code is part of a larger application (for example a JEE application), then other Analysis Units may also be created:

  • There is nothing further to do, you can now run a test analysis on the Analysis Unit before you generate a new snapshot.

Analysis warning and error messages

 Click here to expand...

The following table lists the errors and warnings that may occur during when analyzing source code with the AngularJS extension:

Message ID
Message Type

Logged during

Impact
Remediation
Action
ANGULARJS-001WarningAnalysisA link could not be created because of an internal error.

 

Contact CAST Technical Support
ANGULARJS-002WarningAnalysisSome directories seem identical and perhaps source code is duplicated. Results will be more accurate without duplication of source codeRemove duplicated source code to improve accuracy of results. 
ANGULARJS-003WarningAnalysisAn html file could not be analyzed. If the html file is empty, has a strange format, or is not related to AngularJS, you can ignore this warning. Contact CAST Technical Support
ANGULARJS-004WarningAnalysisA file was not full analyzed because of an internal error. Contact CAST Technical Support
ANGULARJS-005WarningAnalysisA file was not fully analyzed because of an internal error. The message will list the source code line numbers that are causing the problem. If nothing important is between these lines you can ignore the message. Contact CAST Technical Support
ANGULARJS-006WarningAnalysisAn html file referenced in a templateUrl property in an AngularJS file was not found. If the referenced html file does not exist, you can ignore the warning. Contact CAST Technical Support
ANGULARJS-007WarningPost analysesInternal issue with a SQL query that prevents the correct parent ibject being assigned to AngularJS applications. Contact CAST Technical Support

  • No labels