p.s. You will need to do an CVS update on the Excalibur i18n package before building the updated Merlin package.
Cheers, Steve.
Stephen McConnell wrote:
Some changes to the Merlin 2.1 bootstrap process have just been comitted. These changes simply the startup process and make the selection of different deployment scenarios a lot easier - however, this change will require updates to existing configuration.
Instead of a seperate kernel.xml and blocks.xml - the two files have been merged.
You kernel.xml should be update to include your <blocks> element as an element embedeed within the <kernel> element. E.g..
<kernel>
<!-- logging stuff -->
<blocks>
<!-- blocks declaration -->
</blocks>
</kernel>
A new bootstrap system has been put in place that used the commons CLI package. To get details of the command line options you can do the following:
$ cd <your-merlin-dir>
$ merlin -help
After updating you kernel.xml file to include the <blocks> element, you would run it up using the following command:
$ merlin -profile <your-kernel-xml-filename>
The demo profile can be executed by doing the following:
$ merlin -profile config/demo.xml
Cheers, Steve.
-- Stephen J. McConnell mailto:[EMAIL PROTECTED] http://www.osm.net
-- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
