This article shows the steps you must follow to execute a deployment from the Command Line Procedure object for the GeneXus Java Generator.
- From the GeneXus Toolbar, go to Build>Deploy Application.
- Choose the "Local" Target to perform a deployment in the local environment.
Choose Package Type = Binaries.
- Then click on the Deploy button.
GeneXus will generate the necessary files for deployment, including the .jar file containing your application and its dependencies.
In the output, you will see the path to the generated .jar file with your application classes:
Therefore, the resulting structure will be as follows:
The .jar file named <DeploymentUnit_Name>_<ProjectName>.jar contains the classes and configuration files needed to execute the procedure.
In a child directory of the deployment folder (in the example "DeploymentUnit2"), you will find all the .jar files that represent your application's dependencies.
Note: The loose .class files that you find in the classes folder are only intermediary and are used to build the final .jar file, but they are not needed to run the application.
To run your application, you only need the main .jar file and all the dependencies specified in the classpath entry. Be sure to include all necessary dependencies according to your application requirements.
java -cp <classpath> package.<classfile>
In addition, when the deployment unit contains only one command line procedure, the deployment process generates a manifest file that contains information about the main class of your application and the classpath required for its execution.
This simplifies the execution process, as you can have the generated .jar file along with the other .jar files indicated in the classpath entry, and easily execute it using the following command:
java -jar <FileName.jar>