An update on this... I have reorganised the build for the GPD. There will be some more changes in the near future without doubt, but for now the situation is as follows: - check out the entire jbpm.3 module and invoke the build target on the build.xml file of the first level build project. This will build all the jbpm artifacts, including the GPD - check out the first level build project of the jbpm.3 module AND the org.jbpm.gd.jpdl.build project that you find in the jbpm.3/designer/jpdl module. Invoking the all target on the build.xml file of this project will produce the GPD artifacts, but only if the userguide archive (which is a zip file) of the matching jbpm version is in your local repository. This userguide archive is produced by invoking the build on the appropriate project. If you don't check out the org.jbpm.gd.jpdl.docs and org.jbpm.gd.jpdl.site projects in your workspace along with the org.jbpm.gd.jpdl.build project, they will be checked out automatically, otherwise the projects of your workspace will be used. Some enhancements for the future: The GPD build checks out the feature project and all the plugin projects automatically (because the Eclipse PDE build does so by default). We would like these plugins and feature not to be checked out if they are in the current workspace. This is an area that is still under development. One final note: if you need to build the GPD, remember that this involves an Eclipse PDE build with all its requirements. The most important requirements of this are the right CVS client and the right Zip/Unzip software on your system path. More info on this is found on the Eclipse website. Regards, Koen View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3960194#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...