Revision as of 07:38, 20 September 2011

Contents

Introduction

This article is meant to give you detailed instructions on how to set up your Workspace in order to build and test XQDT on your machine. The steps described cover setting up minimal dependencies and development environment with Helios Classic. Larger packages will have some of the required features pre-installed.

Eclipse XML Editors and Tools (this will bring down the Structured Source Editor; we are trying to build the new XQuery editor based on this one instead on the DLTK source editor)

Finish the installation wizard and restart your Eclipse.

One mode dependency:

ANTLR Runtime 3.2

The current XQuery parser is generated using ANTLR. ANTLR Runtime 3.2 is available through the Eclipse Orbit project. http://download.eclipse.org/tools/orbit/downloads/. Click on the latest release or stable build and on the build information page copy the update URL under "Orbit Build Repository". Use this URL as an update site in Eclipse. Select andt install "ANTLR Runtime" from the "All Orbit Bundles" category. Make sure this is version 3.2.0, otherwise send us a message. Thanks! ;)

Get XQDT Source from Git

If you are a committer enter your credentials. Thus you will be able to push changes back.

Select xquery-dev branch only, accept defaults after that.

Select the repository you just cloned: org.eclipse.webtools.incubator

Accept the default to "Import Existing Projects".

Click Finish.

You might wanna create new Working Sets to group the projects (in your Package Explorer you must make sure that "Working Sets" is selected in the "Top Level Elements" menu)

"XQDT tests" for all projects having the name ending with "test"

"XQDT features" for all projects having the name ending with "feature"

"XQDT Zorba" for all projects containing "zorba" in the name

"XQDT 28msec" for all projects containing "set" in the name

"XQDT Marklogic" for all projects containing "marklogic" in the name

Now your workspace should not have any other errors that:

Marklogic plugins errors but someone is on it right now.

"An API baseline has not been set for the current workspace." error is showing up in your problem view. Disable it for now from the Preferences > "Plug-in Development" > "API Baselines" by changing the "Missing API baseline" option to "Warning"