type safe templating

Jamon Changes

Eclipse Feature Changes from 2.3.2 to 2.3.3

Processor Changes from 2.3.2 to 2.3.3

Processor Changes from 2.3.1 to 2.3.2

Runtime Changes from 2.3.0 to 2.3.1

Eclipse Feature Changes from to 2.3.1

Jamon Changes from 2.2.2 to 2.3.0

Jamon Changes from 2.2.1 to 2.2.2

Jamon Changes from 2.2 to 2.2.1

Jamon Changes from 2.1 to 2.2

Jamon Changes from 2.0 to 2.1

Jamon Changes from 1.3 to 2.0

Jamon Changes from 1.2 to 1.3

  • Invocations of public methods on templates only throw IOException when there is an IOException on the underlying writer. Other exceptions, e.g. relating to compilation errors of dynamically modified templates, are now JamonRuntimeExceptions. One side effect of this is that invoking Renderer.asString() no longer throws IOException.
  • The character encoding of a template can now be specified via the <%encoding ...> declaration, which, if present, must occur at the very beginning of a template source file.
  • It is now possible to specify what types are legally included in emit (<% ... %>) directives via the EmitMode. This is specifiable for all templates only, by supplying the appropriate attribute to the JamonTask, and via the corresponding attribute on the RecompilingTemplateManager.
  • Jamon Changes from 1.1 to 1.2