Compiling Xtend with buckminster.
... is pretty simple. Create a launch configuratuion file for example /org.xtext.example.mydsl/Xtend compiler.launch:

<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<launchConfiguration type="org.eclipse.jdt.launching.localJavaApplication">
<listAttribute key="org.eclipse.debug.core.MAPPED_RESOURCE_PATHS">
<listEntry value="/org.xtext.example.mydsl"/>
</listAttribute>
<listAttribute key="org.eclipse.debug.core.MAPPED_RESOURCE_TYPES">
<listEntry value="4"/>
</listAttribute>
<stringAttribute key="org.eclipse.jdt.launching.MAIN_TYPE" value="org.eclipse.xtend.core.compiler.batch.Main"/>
<stringAttribute key="org.eclipse.jdt.launching.PROGRAM_ARGUMENTS" value="-d xtend-gen src"/>
<stringAttribute key="org.eclipse.jdt.launching.PROJECT_ATTR" value="org.xtext.example.mydsl"/>
</launchConfiguration>

(Note: MAIN_TYPE prio Xtext 2.3.0 is org.eclipse.xtext.xtend2.compiler.batch.Main)

Launch it with buckminster before build:
// resolve stuff
launch -l "org.xtext.example.mydsl/Xtend compiler.launch"
build

// run tests
// create p2 repository

Very useful: add --stderr and/or --stdout to link standard output to buckminster console:
launch --stderr --stdout -l "org.xtext.example.mydsl/Xtend compiler.launch"
Shared publiclyView activity