EGL Project Manager
For those of you who are following the EGL open source project on Eclipse (you may have read about it in an earlier EGL Cafe blog The open era for EGL begins today), we're excited to announce the availability of our second incubator release, EGL Web Developer Tools 0.8.
In this release, we have made a lot of progress in the areas of generator and debugger extensibility, optimization of the generated code, integration (especially calling IBM i applications and JNDI support), as well as usability and productivity improvements.
Visit the EGL Development Tools home page on Eclipse.org to learn more about the EDT project. You can read about the new features on the New and Noteworthy page, and you'll find more in-depth articles on the EDT Team Blog or you can follow Eclipse_EDT on Twitter for the latest news.
You can help shape the future of EGL by participating in the EDT project. Download the driver, explore the features, and give us your feedback on the EDT Forum. Become a part of our open source community, and maybe even make a code contribution!
EGL Project Manager
If you are creating an automated build process for an EGL application, you will want the build to start with an empty workspace and load the application source files from the latest committed changes in the Source Control Manager repository. This example demonstrates how to use Ant builds to:
When loading from a CVS repository, you identify the projects you want to load in an Eclipse project set (.psf) file. The command file uses the RAD projectSetImport Ant task (shipped in RBD) to import the projects named in the project set file. Which project is loaded by this sample is not
important; the purpose is to show how to load a project from CVS.
You can create a project set file for projects in your own repository by checking
out the projects into RBD and clicking on “Export, Team, Team Project
Set”. The command is a misnomer; it does
not export the projects you select.
Instead it creates a project set file with an entry for each project
identifying the project, branch, and team server from which the project can be
checked out or loaded.
Loading a Project from a Rational Team Concert Repository
With RTC, you specify the projects that you want to load by defining a “repository workspace” to RTC and include the projects you want to load in the repository workspace. The command file uses the teamFetch Ant task to load the projects from the repository workspace into the local RBD workspace.
Capturing your own Empty Workspace
capture a workspace:
captureWorkspace d:\workspace_CVS workspace_CVS.zip
can export project set files with an “SVN nature” if the Subversive Team Provider is installed in your RBD,
but the projectSetImport Ant task does not appear to work with SVN project set
Appendix: Files provided in the example
Ant build files:
Workspace zip files: