Jbase is a reusable Xtext Expression language: it is a customization of Xtext Xbase to deal with pure Java expressions and statements.
Eclipse Update Site
Zipped update sites: https://dl.bintray.com/lorenzobettini/xtext-jbase/zipped
Please make sure you add the Xtext update site (http://download.eclipse.org/modeling/tmf/xtext/updates/composite/releases/) before you install Jbase features, so that all the requested Xtext bundles, with the specific version required by Jbase, are found.
Please make sure to use the version of Jbase that corresponds to the version of Xtext you want to use. You can find the right version by looking at the update site category that is of the shape, for example
Jbase 0.6.x (for Xtext 2.11.0)
If you want to make sure you do not upgrade to a newer version of Jbase by using the "All releases" update site, you can use the update site of a specific major.minor version, for example, for version 0.6.x you can use the update site
Maven Artifacts for Jbase are available from Maven Central (both releases and snapshots), in case you need to process your DSL files with the xtext-maven-plugin. An example can be found in the project jbase.example.client.maven.
The groupId and artifactId are as follows
<dependency> <groupId>net.sf.xtext-jbase</groupId> <artifactId>jbase</artifactId> <version>...</version> </dependency>
Jbase assumes that you are already familiar with Xtext and in particular with Xbase concepts.
The Jbase SDK that you install in Eclipse comes with (currently small) documentation in Eclipse format. The same documentation can be browsed online.
Contribute to Jbase
We provide an Oomph setup, which is available from the official Oomph catalog.
Compiling From Sources
If you want to build Jbase update site locally, you need Maven.
First of all, make sure to increase memory
export MAVEN_OPTS="-Xmx512m -XX:MaxPermSize=256m"
Then cd to jbase.releng directory and run
mvn clean verify
You will find the p2 update site in the target directory of the jbase.site project.
The above command will also execute all the tests, including UI tests that will run Eclipse instances (you will see Eclipse appear at some point during the build).
If you want to skip tests, you should run the following command instead of the previous one:
mvn clean verify -DskipTests