If you are a Folio developer, you have to consider following additional aspects when working with app.ducx projects.
Additional contents may be specified within Fabasoft app.ducx project settings. It is solely for additional contents, e.g. help contents (Compiled Help Files) or contents for a specific platform, e.g. Windows x64 only. These contents will be part of your software component.
Contents are simply added by dropping a bunch of files from the file system. Additional properties may be set after drop. The basename is initially constructed from the basename of the file. The type is CCT_NORMAL by default. The basename may be changed.
Fabasoft app.ducx tries to identify available variables. The longest match is used. Variables include environment variables and variables available within in Eclipse.
Note: When using a build process out of eclipse, Eclipse variables might not be available.
Running app.ducx in Eclipse requires the setting “Project” > “Build Automatically” to be enabled, so that cross-referencing between different source code sections can be established. This setting will be automatically enabled once after installing the Fabasoft app.ducx feature.
Generating output of a Fabasoft app.ducx project is done by the Fabasoft app.ducx builder. This builder can be configured to run on each automatically triggered build by the Eclipse Platform. The corresponding setting (“Generate COO-file on automatic build”) has to be set in each project’s preferences. By default, this setting is disabled because generating output is not necessary on each save operation in Eclipse.
Exporting a Fabasoft app.ducx project allows you to distribute your project to customers. A Fabasoft app.ducx project represents a single software component. Related software components can be encapsulated in a software product. Several software products build up a software edition. A software edition is a complete product. To customize a software edition depending on customer wishes is done with a software solution.
Software products, software editions and software solutions are defined as instances within a Fabasoft app.ducx project.
In Eclipse, open the “File” menu and click “Export”. Navigate to “Fabasoft app.ducx” > “Extract Component” to export your Fabasoft app.ducx project to a container file (with a .coo extension) that can be installed in another domain by loading it using the management tool.
Exporting Software Products, Software Editions, and Software Solutions
In Eclipse, open the “File” menu and click “Export”. Navigate to “Fabasoft app.ducx” > “Extract Solution” to export a software product, software edition or software solution of your Fabasoft app.ducx project.
The following Java-specific environment variables may be used in the Fabasoft app.ducx project file. If this is the case, make sure that the environment variables are also set in the build environment or that the corresponding values are defined in the Apache Ant build.xml.
Environment variable for the java compiler.
If you compile a Fabasoft app.ducx project containing Java source code, the manifest of the generated JAR file can be populated with following environment variables:
To create a setup kit including your own software solution perform the following steps:
The base product extended by your own software solution can now be installed or updated using setup.exe or setup.sh.