
While we support both Buck and Maven, these names are confusing because which target to launch depends how the project is imported into Eclipse. This is especially bad for gwt_debug (Buck) vs. gwtui_debug (Maven), but it's worth disambiguating for the rest as well. Change-Id: I058e2fddef26b182ae0836a3d8337671be62ac12
17 lines
1.3 KiB
XML
17 lines
1.3 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/buck-out/gen/lib/gwt/dev/gwt-dev-2.5.0.jar"/>
|
|
</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>
|
|
<stringAttribute key="org.eclipse.jdt.launching.MAIN_TYPE" value="com.google.gwt.dev.DevMode"/>
|
|
<stringAttribute key="org.eclipse.jdt.launching.PROGRAM_ARGUMENTS" value="-startupUrl / -war ${resource_loc:/gerrit}/buck-out/gen/gerrit-gwtui/ui_dbg__tmp/war -server com.google.gerrit.gwtdebug.GerritDebugLauncher com.google.gerrit.GerritGwtUI"/>
|
|
<stringAttribute key="org.eclipse.jdt.launching.PROJECT_ATTR" value="gerrit"/>
|
|
<stringAttribute key="org.eclipse.jdt.launching.VM_ARGUMENTS" value="-Xmx256M -XX:MaxPermSize=128M -Dgwt.persistentunitcachedir=${resource_loc:/gerrit}/buck-out/gen/gerrit-gwtui/ui_dbg__tmp/unit_cache -Dgerrit.source_root=${resource_loc:/gerrit} -Dgerrit.site_path=${resource_loc:/gerrit}/../test_site -da:com.google.gwtexpui.globalkey.client.KeyCommandSet"/>
|
|
</launchConfiguration>
|