The Folder option is designed for target source code that is already expanded in a folder (local or network). The option has two functions:
- To package any type of source code supported by CAST (see the CAST Release Notes) stored in a file folder
- This option is also displayed for the following options, mainly to resolve packaging alerts:
- OSGi plugins on your file system > choose the Eclipse "plugins" folder
- Maven repository on your file system > choose the Maven repository folder
- .NET Assemblies on your file system > you need to create multiple packages to package the .NET framework and to resolve packaging alerts, as follows:
|Package name/type||Mandatory?||Location/path||When to create this package|
|External assemblies (third party DLL)||No, only if required: one package per vendor.||N/A: depends on the third party||This package should only be created when your application uses third party assemblies.|
|.NET framework (system assemblies)|| |
|C:\Windows\Microsoft.NET\Framework64\<use the version used by your projects>||If "C:\Windows\Microsoft.NET\Framework64\<use the version used by your projects>" is NOT available on the machine, please use the most recent framework installed on the machine instead: "C:\Windows\Microsoft.NET\Framework64\<use the most recent>". |
Unlike in previous releases of CAST AIP, the .NET analyzer no longer tries to extract the .NET framework assemblies during the analysis: this is why a specific package for external assemblies must be created in the CAST Delivery Manager Tool. If this package is not created and delivered, the .NET analyzer will skip all projects having a dependency to .NET assemblies, leading to incomplete analysis results.
|Custom assemblies||No, only if required: typically when there are unresolved alerts||Source code root folder (or "bin" sub-folder)|| |
The folder does not need to be available during the analysis process in the CAST Management Studio because the CAST Delivery Manager Tool will extract the source code from the folder and package it before delivery to Source Code Delivery Folder.
|Root folder||Enter the location of the folder that contains your target source code - or use the browse button to locate the folder you require. This can be a network location or a folder on your local machine.|
When you have selected one of the following, various additional options will become available:
|Automated extraction of required jar files||OSGi plugins on your file system|
|Maven repository on your file system|
|Automated extraction of required .NET assemblies||.NET Assemblies on your file system|
The aim of these options is to enable you to specify specific elements that you know need to be extracted in order to resolve a packaging alert. You can specify the following items:
|OSGi plugins on your file system||Bundles|
|Maven repository on your file system||Artifacts|
|.NET Assemblies on your file system||.NET framework/Assemblies|
If you do not specify an element, the CAST Delivery Manager Tool will automatically populate the list of elements when you run the Package action based on what it discovers in the root folder you have selected.
|Use this button to add a new element.|
|Use this button to edit an existing element.|
|Use this button to remove an existing element.|
Note that if you change the the projects that have been selected in other packages, then you must clear this list and allow it to be rebuilt automatically.
Advanced Extraction Settings
Please see Source Package - Where is your source code? for more information about these sections. Note that these options are not available for the following options:
- OSGi plugins on your file system
- Maven repository on your file system
- .NET Assemblies on your file system