Using a mechanism of property files for describing services is good enough:
- easy to support
- flexible: allows to describe whatever we need
- human readable

One problem with using it I bumped into - some magic is used, like
native.pattern = %p

To get things better:
- a readme file should be provided
- in all property files that readme file should be mentioned
- the readme file should:
  * general description of what should be provided os.properties files
  * list all "fields" supported by mechanism: args, app, pattern, etc
  * a few examples given