=======================================================================
iEat Release Notes
@VERSION@ @BUILD_DATE@
=======================================================================

Major new features:

- "Live Demo" release (as a separate download).

- Ability to disable user self registration (see the 
  WEB-INF/classes/env.properties file).

- Ability to disable anonymous access, so users must log in to even 
  view recipes (see the WEB-INF/classes/env.properties file).

=======================================================================

NOTE: iEat now relies on the servlet container it runs in to provide
      the javax.mail.Session for sending emails. This requires a 
      slight configuration change to your servlet container if you 
      are upgrading from a previous release. See the README that comes
      with this release for more info.

=======================================================================

Changes since last release:

- Minor XSLT bug fix for exporting RecipeML.

- Nicer formatting in XSLT output for exporting recipes as text. Now 
  recipes used as ingredients are included in output and referenced 
  from main recipe.
  
- Added AppContext support for passing application parameters to 
  views.
  
- Statically cache JAXBContext objects across all views to minimize 
  number of JAXBContext objects created.
  
- Added ability to disable user self-registration and disable 
  anonymous user access. These features are controlled by the 
  'feature.registration' and 'feature.anonymous' properties in the 
  <IEAT HOME>/WEB-INF/classes/env.properties file.
  
- Upgraded to Spring 1.1.5 release.

- Fix for Lucene exception thrown during index browsing when nothing 
  had been indexed yet.
  
- Altered mail configuration to use JNDI-based javax.mail.Session 
  object. This allows the servlet container to control the mail 
  settings.
  
- Finished incomplete implementation for supporting multiple resource 
  bundles in MessagesSource class, and broke recipe domain object 
  messaged out into own 'domain-messages.properties' file for 
  easier management.
  
- Implemented "Live Demo" release which bundles a pre-configured 
  Tomcat container and Derby database and runs "out of the box" 
  without any configuration changes.
  