From bemoko developer wiki

Released on 5 January 2010

Summary

1.2.5 is an upgrade from the 1.2 branch of bemokoLive, it is now the recommended version of bemokoLive.

The headline features for this release is the support of sub-sites and context rules - which give you better control for campaign management, site reuse and user context. Documentation on these features will follow shortly ...

Over and above 1.2.4 it includes the following changes:

Upgrading from a previous release

• Previous verisions included the preconfigured sites location directory of /opt/local/bemoko/sites which has now been replaced with [user home]/bemoko/sites. If you need to use the old location, add /opt/local/bemoko/sites to your local WEB-INF/live-config.xml or add the following parameter to your JVM: -Dbemoko.sites.location=/opt/local/bemoko/sites

Enhancements

• Context rule support, e.g. support the ability to set the ui to use in the intent URL to allow explicit user override (#61)
• Tweaker initialise not executed (#1313)
• Template not found exception not clear (#1558)
• AbstractRendererPlugin now has access to database and findResource in AbstractPlugin (#1726)
• wgz / nokia widget mime type added (#1758)
• plist mime type added (#1825)
• On screen error report should include relevant stacktraceelement even if beyond 5 elements (#1892)
• Add Bemoko object as convenient platform API (#1962)
• Add 480 UI to default site (#1963)
• Ehcache upgraded to 1.7.0 (#1967)
• Groovy upgraded to 1.7.0 (#1993)
• Support for sub-sites (#1966)
• Add tutorial site (#1983)
• Add configuration to enable or disable caches (#1985)
• Provide a way of disabling om/dev functionality in production (#1990)
• Include cache settings on welcome page (#2002)
• Replace /opt/local/ with user's home directory in sites configuration (#2005)

Fixes

All the following have been fixed:

• Freemarker #include by aquisition didn't work (#1840)
• Multiple value intent parameters were not supported, e.g. multi-value form fields (#1890)
• Tweaker inherit="false" was not being inherited properly in site configuration inheritance (#1975)
• AbstractLivePlatformConfiguration.getAbsolutePathToFile was not Windows compatible (#2006)