c69f360714
To guess what build system is used, we create now .primary_build_tool file in the root of the project during the eclipse classpath generation. Change the working directory for GWT SDM session to be .gwt_work_dir. The reason for that Bazel doesn't allow to write to bazel-out. Change-Id: I984068350244ee9d66807e4bc8c6779b34a26bab
18 lines
1.1 KiB
XML
18 lines
1.1 KiB
XML
<?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="/gerrit/gerrit-main/src/main/java/Main.java"/>
|
|
</listAttribute>
|
|
<listAttribute key="org.eclipse.debug.core.MAPPED_RESOURCE_TYPES">
|
|
<listEntry value="1"/>
|
|
</listAttribute>
|
|
<listAttribute key="org.eclipse.debug.ui.favoriteGroups">
|
|
<listEntry value="org.eclipse.debug.ui.launchGroup.debug"/>
|
|
</listAttribute>
|
|
<booleanAttribute key="org.eclipse.jdt.launching.ATTR_USE_START_ON_FIRST_THREAD" value="true"/>
|
|
<stringAttribute key="org.eclipse.jdt.launching.MAIN_TYPE" value="Main"/>
|
|
<stringAttribute key="org.eclipse.jdt.launching.PROGRAM_ARGUMENTS" value="daemon --console-log --show-stack-trace -d ${resource_loc:/gerrit}/../gerrit_testsite"/>
|
|
<stringAttribute key="org.eclipse.jdt.launching.PROJECT_ATTR" value="gerrit"/>
|
|
<stringAttribute key="org.eclipse.jdt.launching.VM_ARGUMENTS" value="-Dgerrit.plugin-classes=${resource_loc:/gerrit/eclipse-out}/plugins"/>
|
|
</launchConfiguration>
|