-
Notifications
You must be signed in to change notification settings - Fork 4
How to apply MOGLiCC?
Back to the User Guide overview
The MOGLi Code Creator is released as a zip-file. The last version is found here. After unzipping its content, a lib directory containing the MOGLiCC jar files and a start batch file is present.
Having set the environment variable JAVA_HOME pointing on a 1.6 JRE, the Code Creator will do its job when calling the start batch. When called the first time, some directories are created and a number of default files are extracted from the jar source files.
For each plugin that needs input data, the input directory contains a subdirectories named after the corresponding plugin. Each generator scans its input subdirectory for input artefacts. An input artefact consists at least of one template file. The same subdirectories exists in the output dir, whose content is deleted on every application start. The input and output directories can be organized in different workspaces.
As default the application root directory is used as workspace directory. However, the “application.properties” file allows to move the workspace directory to an arbitrary file system folder. In this way, you can manage code generation for different projects. For more information how to configure a workspace directory read the default application properties file.
B) How to define an input artefact?
C) How to validate MetaInfo elements?
D) How to follow the MOGLiCC workflow?
E) VelocityClassBasedFileMaker vs. VelocityModelBasedLineInserter
H) Using the ExcelStandardModelProvider
I) Injecting static utilities by the dropin mechanism
To study a detailed examples without an IDE have a look on these Hello World Examples.