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

Define project exclusion 

You may now need to exclude some projects that have been discovered and marked with Selected during the initial Package action so that they are not included in the delivery. For example, you may not want to deliver "test" projects, or other projects that are not directly used by the projects you need to deliver. The information gathered during the Application Architecture Review  will help guide the validation of the application boundary and decide what should be excluded from the internal objects and link representation of the analyzed application.

Excluding third party components and, in general, any artifacts which are not relevant to the scope of the analysis will improve the relevance of the results.

To do so, you need to return to the Package Configuration tab for EACH package you have packaged and scroll down to the Projects to exclude section:

Use the Project exclusion sub section to exclude specific projects that have already been discovered by the CAST Delivery Manager Tool:

Exclusion best practices

Strategies and CAST recommended best practices for exclusion/inclusion of various source code types are summarized in the table below:

Source code type
Strategy

Source code created and maintained by Application Team

include

Automatically generated source code

include - as it will be required to discover all links

 Test code

exclude

External binary libraries - Java/App server/frameworks/JARs (contain .class files)

include

Source libraries - Javascript libraries 
(source code provided as .js files)

include

Re-run the Package action

To ensure that the exclusions you have defined are taken into account, you need to re-run the packaging action at Version level (i.e. all packages are re-packaged):

Finally check the Package Content tab to ensure that the projects you have excluded are marked as ignored:

  • No labels