> I leave it to harald to talk about the Incremental Builder.
Sorry I didn't answer right away, I'm rather busy at the moment (large
non-wo project).
The incremental build is aimed at doing simple but fast standard builds of
WO-Applications. It has (currently) a hardcoded list of things it puts into
Resources and WebserverResources and should be faster than the Ant-build by
about a factor of 10.
Unfortunately, it lacks
> Flexibility:
-- it expects a certain project layout (java source in a single
source-folder, Components and Resources anywhere). Compiled classes must be
in a single output folder, build output is put into the build/ folder in the
project root.
It generates very simple Meta-information files, that are barely enough to
let applications and frameworks work, if you work with both WOFrameworks and
WOApplications in the same workspace (and don't have resources and
WebserverResources that are not mentioned in the hardcoded lists), it works
fairly well.
Rapid Turnaround is not needed (and doesn't seem to work properly with
Components in folders and only the PB.project file), since every change to a
file is immediately reflected in the build folder (you have to do a little
magical dance to make WO reread resources).
One big problem with this approach is the fact, that the WOResourceManager
doesn't close files after they have been read. This means that it is
sometimes necessary to stop the application before the incremental builder
can copy WebserverResources into the build folder.
Another advantage of the incremental builder is of course, that it doesn't
trigger the Ant bug :-).
Everyone in our company developing WO Applications uses the incremental
build, and I am under the impression, that they are quite happy with it
(besides the mentioned problems).
Hope this answers the question (at least a little bit).
Harald
This archive was generated by hypermail 2.0.0 : Thu May 15 2003 - 13:38:53 EDT