Conference Calls and Team Meetings
Technical conference calls are held every Tuesday, 4pm CET as EVO meetings. See g-Eclipse wiki for upcoming meetings and meeting minutes.
The conference calls are open to the public, and we invite everyone to participate. All you need is an Internet connection, the EVO software, and a EVO user id. You can get everything you need at evo.caltech.edu.
An introduction to the architecture behind g-Eclipse can be found in the architecture description D1.8.pdf.
Getting the source code: Subversion repository
The source code of the g-Eclipse project can be found in the Subversion repository. It contains the usual SVN directory structure TRUNK, BRANCHES, and TAGS. The development version of the code (HEAD) can be found in TRUNK, milestone and RC snapshots can be found in the BRANCHES directory. The TRUNK directory contains the following substructure:
|doc/||documentation and documentation plug-ins|
|features/||the core feature set of the g-Eclipse project|
|plugins/||the core plug-ins (middleware independent) including eu.geclipse.core and eu.geclipse.ui|
|releng/||everything that is needed for building the feature; at the moment it contains a simple update-site project|
|test/||some JUnit tests|
Setting up your development environment
The easiest way to get your Eclipse environment up and running for taking a look at, or developing with the g-Eclipse code is to download one of the preconfigured g-Eclipse development packages available from Yoxos-on-Demand. Otherwise you can check out from the SVN repository all the single plug-ins by hand, and add the necessary dependencies to your Eclipse installation.
- Open Yoxos-on-Demand
- Choose [Public Profiles|Eclipse Contributors|g-Eclipse Development] or use the direct link: http://ondemand.yoxos.com/geteclipse/start?profiles=868129468_1218707196035418732
- Start the download and unzip the archive
- Start Eclipse and (IMPORTANT) create a *new* workspace
- Disable the automatic build in [Projects|Build Automatically]
- NOTE: If you are behind a proxy, add the appropriate settings in the preferences and restart Eclipse.
- In the bottom right corner you can find the 'Yoxos Notification' window; by clicking on 'Workspace Provisioning update pending' you can start the workspace provisioning which configures Checkstyle, Mylyn, many preferences settings (Java compiler warnings, etc.) and pulls the complete code from SVN and CVS repositories.
- NOTE: Before the provisioning process checks out the projects from CVS, you will be asked for your username and password. Enter your user credentials (or 'anoncvs' as username).
- NOTE: Subversion: This package contains Subversive with two different connectors. By default it uses SVNKit 1.1.7, but some other SVN command line tools of your operating system may require a newer version (e.g. Debian). In that case you can switch to SVNKit 1.2.0 in the preferences.
- Re-enable the automatic build [Projects|Build Automatically] after your new workspace has been created.
- In the preferences ('Team' > 'SVN') switch to the pure Java implementation 'SVNKit', otherwise you will get errors.
- Switch to the 'SVN Repository Exploring' perspective
- Create a new repository location:
- svn+ssh://XXXXXXX@dev.eclipse.org/svnroot/technology/eu.geclipse - where XXXXXXX is your Eclipse Foundation user id
- Now you can browse the SVN repository.
- Check out all the plug-ins from TRUNK as single projects into your workspace.
Additional middleware specific implementations
Why not start with an implementation of your Grid middleware specific extensions? If you want to get your Grid middleware connected, please contact us on the developer mailing list and have a look at the already available implementations.