Everything prepared for Galileo

Last night I fixed the last bug for Eclipse Galileo. Just in time! Today the release candidate RC5 is built for version 0.6 of our project Java Workflow Tooling (JWT) and this release candidate will be used in the final Eclipse Galileo build. You'll find JWT on the Galileo update server in the area General Purpose Tools.

But this doesn't mean that we'll now have time to rest and lie in the sun. Now is the time to summarize the development in JWT of the last months in a few sentences for articles and blogs. It's also the time to plan ahead: how shall the project plan for the next years look like? Which releases will we have and how will the general strategy for e4 as well as beyond look like?


In addition to that there are also integrators of JWT that need to be updated with the new version. In our SourceForge project AgilPro we have a toolsuite that allows to model, simulate and execute workflows. It includes all the plugins (e.g. workflow editor but also several transformations) from the JWT Galileo release.

In addition it also contains the Workflow codegeneration framework which allows us to transform the graph-based to a block-based structure in order to generate BPEL-code (1). So we are just updating and adapting everything until next week in order to have hopefully a joint release of Galileo and AgilPro.

(1) I know that BPEL is not only a block-based language, but can also be used graph-based. But the block-based structure is much better to read and maintain in BPEL-editors.