Package: Check Dependencies
The module is able to check if the dependencies of a package are fullfilled in a client. Therefore a package archive or the package name and the dependency definitions has to be provided. The results of the check will be written to the report. Optionally the results can be written to a variable object.
Designation
- Name
- pm.DependencyCheck
- Aliases
- DependencyCheck, pm.PackageDependencyCheck
Configuration
- Ausgabe
- Optionen
- Variable Object (
variable
) - Name of the variable object that will be just for storing the data
- Variable Source Connection (
variable-source
) - If given it defines an alternative b4A connection where to find the variable objectMögliche Werte: <TabItem b4A Verbindungen>
- XML Variable (
xml-variable
) - name of the XML variable object used to store the information
- Key (
xml-variable-key
) - key in the XML variable object to use
- XML Variable Source Connection (
xml-variable-source
) - If given it defines an alternative b4A connection where to find the variable objectMögliche Werte: <TabItem b4A Verbindungen>
- Mode (
mode
) - Defines if the package and dependency information should be read from a package file or if they are passed on as optionsMögliche Werte: Package Archive (
file
), Options (option
)
- Package (
package
) - Name of the package
- Dependency Definitions (
dependencies
) - The dependency definition of the package to check
- Package Release File (
zip-file
) - Absolute path to the Package release file
Output
The output can be to a static or an XML variable. Theoretically, both at the same time.
Static variable
The static variable, which contains the result of the analysis, stores the following values in the individual columns:
-
Key: Counter
-
Value 1: Name of the package
-
Value 2: Operator of the dependency definition
-
Value 3: Version of the dependency definition
-
Value 4: Status
- OK: The dependency definition matches in the target client
- MISSING: The package is not installed in the target client
- FAILED: The package is installed, but does not match the version comparison
-
Value 5: Installed version (for FAILED status)
XML variable
If the result is written to an XML variable, the data is saved in the following format.
<best4Automic version="5.3.0">
<pm>
<package name="B4A.PM">
<dependencies>
<dependency operator="~=" package="B4A.WEB" version="2.0.0">
<status>FAILED</status>
<installed version="1.0.0"/>
</dependency>
<dependency operator=">=" package="B4A.TEST" version="1.3.4">
<status>MISSING</status>
<installed version=""/>
</dependency>
<dependency operator="~=" package="B4A.BASE" version="1.0.0">
<status>OK</status>
<installed version="1.0.0"/>
</dependency>
</dependencies>
</package>
</pm>
</best4Automic>