Introduction
IntroductionThe configuration is normally stored in the dist/conf-directory. On Unix-platforms Hawron stores the configuration in the $USER_HOME/.hawron/conf-directory.
You can set some options via CLI or the configuration-file 'main.conf' in the 'conf'-directory.
| CLI | Configuration-file | Note |
| -projectfile /path/to/projectfile.hconf | projectfile=/path/to/projectfile.hconf | This can be too a Cocoon-'cli.xconf'-file. |
| -lookandfeel class-name | lookandfeel=class-name | You can download 'Look and Feel's from javootoo.com. Place the jar in lib/optional and set the class-name of the Look and Feel. Or you set the class-name to 'platform' to get your the Look and Feel of your platform. |
| no setting | jre.logging=true/false (default:false) | This will write all messages (stderr,execptions and stdout) to dist/jre.log |
Hawron can import the Cocoon 'cli.xconf'-files. Separate uri-list-files are ignored at the moment.
The application normally translate all paths to absolute paths. You can generate relative paths by choosing the "relative paths"-option inside the "Save" or "Save as"-Dialog, all paths are then created relative to the location of your CLI-Config file, if it possible.
It might be good idea to work with a copy of your 'cli.xconf'-file. Simple use 'Save as' to generate a copy and use this.
Hawron can export the project as 'cli.xconf'- or Ant-buildfile. Simple use 'Save as' and select the file-format of your need. In this case you can use Cocoon from the CommandLine or with Ant. So you can use Cocoon's Offline Generation with shell-scripts or cronjobs
Cocoon doesn't support publishing, Ant does but it is not implemented as yet (comes in a later release).