Creating a new project

1.  Introduction
2.  Installing Invicta
3.  Creating Directory Structure
4.  Customizing Template Project
5.  Running Invicta

1. Introduction

Starting a new Invicta project is rather simple.  All you need to do is follow a few steps, and you're up and running.  To make things even simpler, you may use the New Project Template which is part of the distribution to a new location, and edit it.

You should also take a look at the sample projects that are part of the distribution (sample and sample2 directories).

Following is a detailed description of the required actions for creating an Invicta build project.

Return to top

2. Installing Invicta

The installation of Invicta is performed by simply extracting the ZIP file of Invicta ( into your desired installation location. You may want to install Invicta in a global location, where multiple projects can access.

Invicta distribution has the following structure and files:

    README.txt  - General information about Invicta distribution content.
    /lib - Run-time libraries required for running Invicta.
       invicta.jar - The JAR file of the Invicta application.
    /types - Built-in component types.
    /docs - Invicta's complete manual.
    /template - A new-project template.  



- A sample project.
    /sample2 - Another sample project that depends on the first sample projet.


3. Creating Directory Structure

The first step is creating a project home directory somewhere.  Under it there should be a directory for each project component, such that component hierarchy is reflected in the directory structure.  For example: component myproj.comp1 should reside in <Project_Home>/comp1, and myproj.comp1.comp2 in <Project_Home>/comp1/comp2.

Each component's type requires a specific directory structure created under the component's directory. The following notes describe the default directory structure of JAR and WAR components:

You need an access to an installation directory of Invicta, where Invicta's JAR files and built-in Types are located..  Another directory, consisting of project definition files, custom properties for ANT compilation time and custom files (Types, Handlers and Dumpers, if you have them), should be created.  There should also be a separate directory for the output files, for example, an /env directory for the build.xml file generated by AntDumper.

Return to top


4. Customizing Template Project

You may manually create your scripts and properties files for running Invicta, but you may also copy the content of the template directory of the distribution into your new project's location and customize it:

The template project contains the following files:

Return to top

5. Running Invicta

That's it!  Activating the Invicta running script will produce the output files you need. Refer to Invicta Usage for more details.

Return to top