[Bodington-developers] Latest additions to bodington (- lxsocon).

[Alexis O'C. <ale...@co...>]

Just an update regarding stuff I was marked down for at the last 
developers meeting (28th/29th April). This is just a summary of recent 
changes I've made (with the rationale). For a full list do a diff on the 
dates 2005-05-28 < '2005-05-05 11:00' (or the 'commit sets' feature of 
Eclipse within the team synchronize perspective).

branch: bodington_2_4

org/bodington/servlet/template/LegacyTemplate.java
org/bodington/servlet/template/XmlTemplate.java
[lxsocon] (29-Apr-2005 16:57:53) Modified to use simpler straight call 
to com.sun.tools.javac.Main for java compilation stage. Fixed for JDK 
1.5 too.

build.xml
[lxsocon] (29-Apr-2005 17:14:56) Modified compile targets to compile 1.4 
source (enables build to work on JDK 1.5).

In combination enable bodington to compile on JDK 1.4.0 - 1.5 (you 
*must* specify 'source=1.4' for the latter) and run on all these 
platforms without further changes.

branch: HEAD

- as above -

"A total of 50 files"
[lxsocon] (04-May-2005 14:43:37) Java 5: changed every occurence of 
'enum' as identifier to 'enumeration' (it is a reserved keyword in Java 5).

'enum' is now a reserved keyword in JDK 1.5 / Java 5. There were about 
800(!) places where enum was used as an identifier (for objects of type 
'java.util.Enumeration' strangely enough!). This wrecks building 
bodington on Java 5 (with source=1.5 - the default). Therefore, every 
occurance of 'enum' as an identifier has been changed to 'enumeration'.

build.xml
Due to changes made elsewhere, it is now possible to build and run on 
JDK 1.5. Via use of an added context.xml file it is now possible to 
perform a deploy-local, i.e. deploy bodington from a docBase anywhere on 
your machine, into Tomcat 5.5 (running on J2SDK 1.4.2 - JDK 1.5).

"Template compilation"
Changes have been made to classes involved in template compilation, i.e. 
those called from the 'compile-templates' target in build.xml, for an 
improved 'design-time' experience. Essentially, (optional) richer more 
accurate warnings regarding problems in the XML parsing stage, much 
reduced verbosity when compilation is not necessary / does not occur. 
This is part of ongoing work. I intend to also implement the following:

- optional 'fail on build' for template compilation.
- handling of FileSets (e.g. <include name=**/*.html />).
- better error reporting for java to bytecode compilation stage.


Alexis