Deployment Check Utility

Scope

Languages: Java

Introduction

In some cases, when building application deployments, a desynchronization has been detected between the Jar classes content and the model directory classes content.

The Deployment Check utility has been implemented, which allows comparing a deployment content (.jar) with the model directory content.

Description

To call this utility you must have the GxUtils?.jar in the classpath . Then, you call it from Developer Menu - Utilities - Deployment Check:



Firstly, Deployment Check request the path to the .jar to be compared:



By default , the comparison will be performed against GeneXus model directory from which Deployment Check was called. The following screen will be displayed:



Two sections are shown here; the left one shows information on the jar content and the right one shows information on the model directory content.

Each row indicates information on each one of the classes:

Type
The class may be of the following types:
"o" - The content of this class is the same as the one of the other section.
"*" - This file is not found in other section.
"D" - The content of this class is different.

File
It indicates the name of the class or file.

Date
It indicates the date of the class modification.
In case of the .jar created by jar deployment, this date represents the jar creation date; that is to say, all classes will have the same date.

Then, they are counted with actions that allow filtering the files according to the type:
All - it shows all the section files
Equals - it shows the files that have the same content as the one of the other section
Diff - it shows the files that have some difference in their content as regards the same files of the other section. To establish a difference between the files, you do not take into account the files date but their content. E.g.: if a class is regenerated without making any change and it is compiled with the same compiler, it will not appear as different in spite of having a different date. On the other hand, if it is generated with a new generator build or compiled with a different compiler (or a new version of the same compiler), the content will change
Unique - it shows the files existing in this section that DO NOT exist in the other one.