From: Tom Tromey <tromey@redhat.com>
To: Mauve Patch List <mauve-patches@sources.redhat.com>
Subject: Patch: FYI: update eclipse builder
Date: Tue, 28 Feb 2006 19:12:00 -0000 [thread overview]
Message-ID: <m37j7fqq0p.fsf@localhost.localdomain> (raw)
I'm checking this in.
This changes the eclipse 'configure' builder so that it only runs if
configure, Makefile.in, or gnu/testlet/config.java.in changes.
This lets the MauveTestlet runner work more nicely -- now it avoids
that pesky re-running of configure. (If you were at FOSDEM you saw
this in the demo...)
Tom
2006-02-28 Tom Tromey <tromey@redhat.com>
* .project, .externalToolBuilders/ConfigureMauve.launch: Updated
configure builder.
Index: .project
===================================================================
RCS file: /cvs/mauve/mauve/.project,v
retrieving revision 1.1
diff -u -r1.1 .project
--- .project 18 Aug 2005 01:59:02 -0000 1.1
+++ .project 28 Feb 2006 18:44:17 -0000
@@ -7,7 +7,7 @@
<buildSpec>
<buildCommand>
<name>org.eclipse.ui.externaltools.ExternalToolBuilder</name>
- <triggers>full,incremental,</triggers>
+ <triggers>auto,full,incremental,</triggers>
<arguments>
<dictionary>
<key>LaunchConfigHandle</key>
Index: .externalToolBuilders/ConfigureMauve.launch
===================================================================
RCS file: /cvs/mauve/mauve/.externalToolBuilders/ConfigureMauve.launch,v
retrieving revision 1.1
diff -u -r1.1 ConfigureMauve.launch
--- .externalToolBuilders/ConfigureMauve.launch 18 Aug 2005 01:59:03 -0000 1.1
+++ .externalToolBuilders/ConfigureMauve.launch 28 Feb 2006 18:44:17 -0000
@@ -1,2 +1,12 @@
-<?xml version='1.0'?>
-<launchConfiguration type='org.eclipse.ui.externaltools.ProgramBuilderLaunchConfigurationType'><stringAttribute key='org.eclipse.debug.core.ATTR_REFRESH_SCOPE' value='${project}'/><stringAttribute key='org.eclipse.ui.externaltools.ATTR_RUN_BUILD_KINDS' value='full,incremental,'/><stringAttribute key='org.eclipse.ui.externaltools.ATTR_LOCATION' value='${system_path:sh}'/><booleanAttribute key='org.eclipse.ui.externaltools.ATTR_TRIGGERS_CONFIGURED' value='true'/><stringAttribute key='org.eclipse.ui.externaltools.ATTR_WORKING_DIRECTORY' value='${build_project}'/><booleanAttribute key='org.eclipse.debug.ui.ATTR_LAUNCH_IN_BACKGROUND' value='false'/><stringAttribute key='org.eclipse.ui.externaltools.ATTR_TOOL_ARGUMENTS' value='configure'/><booleanAttribute key='org.eclipse.debug.core.appendEnvironmentVariables' value='true'/></launchConfiguration>
\ No newline at end of file
+<?xml version="1.0" encoding="UTF-8"?>
+<launchConfiguration type="org.eclipse.ui.externaltools.ProgramBuilderLaunchConfigurationType">
+<booleanAttribute key="org.eclipse.debug.ui.ATTR_LAUNCH_IN_BACKGROUND" value="false"/>
+<stringAttribute key="org.eclipse.ui.externaltools.ATTR_BUILD_SCOPE" value="${working_set:<?xml version="1.0" encoding="UTF-8"?> <launchConfigurationWorkingSet factoryID="org.eclipse.ui.internal.WorkingSetFactory" name="workingSet"> <item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/mauve/configure" type="1"/> <item factoryID="org.eclipse.ui.internal.model.ResourceFactory" path="/mauve/gnu/testlet/config.java.in" type="1"/> </launchConfigurationWorkingSet>}"/>
+<stringAttribute key="org.eclipse.ui.externaltools.ATTR_TOOL_ARGUMENTS" value="configure"/>
+<stringAttribute key="org.eclipse.ui.externaltools.ATTR_RUN_BUILD_KINDS" value="full,incremental,auto,"/>
+<stringAttribute key="org.eclipse.debug.core.ATTR_REFRESH_SCOPE" value="${project}"/>
+<stringAttribute key="org.eclipse.ui.externaltools.ATTR_WORKING_DIRECTORY" value="${build_project}"/>
+<stringAttribute key="org.eclipse.ui.externaltools.ATTR_LOCATION" value="${system_path:sh}"/>
+<booleanAttribute key="org.eclipse.ui.externaltools.ATTR_TRIGGERS_CONFIGURED" value="true"/>
+<booleanAttribute key="org.eclipse.debug.core.appendEnvironmentVariables" value="true"/>
+</launchConfiguration>
reply other threads:[~2006-02-28 19:12 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m37j7fqq0p.fsf@localhost.localdomain \
--to=tromey@redhat.com \
--cc=mauve-patches@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).