Install the tools needed in the IDE to work with the source code for ${scope.project.label}
Set the heap space needed to work with the projects of ${scope.project.label}
Initialize JDT's package explorer to show working sets as its root objects
<?xml version="1.0" encoding="UTF-8"?>
<section name="Workbench">
<section name="org.eclipse.jdt.internal.ui.packageview.PackageExplorerPart">
<item value="true" key="group_libraries"/>
<item value="false" key="linkWithEditor"/>
<item value="2" key="layout"/>
<item value="2" key="rootMode"/>
<item value="<?xml version="1.0" encoding="UTF-8"?>
<packageExplorer configured="true" group_libraries="1" layout="2" linkWithEditor="0" rootMode="2" sortWorkingSets="false" workingSetName="">
<localWorkingSetManager>
<workingSet editPageId="org.eclipse.jdt.internal.ui.OthersWorkingSet" factoryID="org.eclipse.ui.internal.WorkingSetFactory" id="1382792884467_1" label="Other Projects" name="Other Projects"/>
</localWorkingSetManager>
<activeWorkingSet workingSetName="Other Projects"/>
<allWorkingSets workingSetName="Other Projects"/>
</packageExplorer>" key="memento"/>
</section>
</section>
Define the JRE needed to compile and run the Java projects of ${scope.project.label}
OMG! We have circular dependency that involves 'java.package; org.eclipse.cdt.utils.pty 0.0.0'
but it gets resolved here as we have CDT repo below.
An API baseline based on the target platform named 'Modular API Baseline Target'
We explicitly have CDT in target platform so that developers can develop org.eclipse.cdt.core/ui without requiring all the projects from CDT in their workspace.
eclipse.git.gerrit.remoteURIs
${scope.project.label} Git or Gerrit Repository
remoteURI
CDT
The dynamic working sets for ${scope.project.label}
C/C++ Development Tools