Page History

...

• Start up eclipse
• Switch to the Java perspective
• Right click in the Package Explorer frame on the root of the newly created project and select Properties => Java Build Path
• Click on the "Libraries" tab and select "Add Variable...", "Configure Variables ...", "New ..."
• Set Name to M2_REPO and Click on "Folder..."
• Navigate to the "repository" folder/directory (on Windows this is \Documents and Settings\<user>\.m2\repository, on Linux it is ~/.m2/repository) and click OK
• Now execute "File => Import ... => General => Existing project into workspace
• Click "Browse ..." Navigate to the <sdo-source-root> directory and click OK
• Select all projects and click OK
• When building is complete the projects should now have no errors

At this point you have three seven separate projects each dependent on binary artifacts in your maven repository. Don't be tricked into thinking that
if you modify the sdo-impl project, that those changes will be picked up by the sdo-tools project. If you want this behavior then follow these steps

...

With EMF being such an integral part of SDO development, its often necessary to debug into the EMF code to understand what's going on. To do this you need to download an EMF SDK (runtimesruntime, source, docs) for EMF, SDO and XSD (Don't be confused by the presence of SDO; the version 1 API used to be developed at Eclipse, and it is this that is being downloaded, you can safely ignore it). You'll need the corresponding EMF version to the Tuscany SDO source code (Currently EMF 2.2.3 as at January 2008). Take a look for the <emfVersion> tag in the sdo/pom.xml file to discover the current version dependency. Extract the downloaded archive to somewhere on your computer.

...