Application Descriptor

A Roboconf project must contain a descriptor directory with an application descriptor inside.
This descriptor must be named

It contains basic information related to the application itself.
Here is a sample you can copy / paste and edit.

# Application Descriptor for Roboconf

# The application name (required)
# It should be readable by a human.
name = Your Application Name

# The application version (required)
# It must follow this convention:
# <major>.<minor>.<patch>.<qualifier>
# or
# <major>.<minor>.<patch>-<qualifier>
# Major, minor and patch must be numbers.
# Qualifier can be any string.
# The patch number and the qualifier are optional.
version = snapshot

# The application's description (optional)
description = The description of \
your application

# Tags to describe the template (optional)
tags = tag 1, tag 2, etc.

# The DSL ID (optional)
# For the moment, Roboconf only knows 1 DSL,
# but it may support other standards or definitions later.
dsl-id = roboconf-1.0

# The main graph file (required)
# A graph definition may contain several files. This property indicates
# the one to read first.
graph-entry-point = main.graph

# The main instances file (optional)
# An instance definition may be made up of several files. This property
# indicates the one to read first.
instance-entry-point = definition.instances

Advanced Properties

Additional properties can appear in this descriptor.
See the page related to inter-applications dependencies for more details.

Maven Integration

By using the Roboconf Maven plug-in, it is possible to inject Maven properties in the descriptor.

name = Tomcat 8 cluster
version = ${project.version}

# Etc.