| Incremental builder vs. External tools launch configuration [message #331757] |
Fri, 19 September 2008 17:42 |
 Richard Bone
Messages: 13
Registered: July 2009 |
Junior Member |
|
|
Hi,
I've implemented a launch configuration type that the external tools
builder is spawning when a project gets built. One problem, though, is
that the builder seems to not always run on other user's machines. Some
people have had to explicitly do a build project, while others have had to
close their project and reopen and then do a manual build.
Our .project has a build command for the external tools builder that looks
like this...
<buildCommand>
<name>org.eclipse.ui.externaltools.ExternalToolBuilder</name >
<triggers>full,incremental,clean</triggers>
<arguments>
<dictionary>
<key>LaunchConfigHandle</key>
<value> <project>/.externalToolBuilders/New_Builder.la unch </value>
</dictionary>
</arguments>
</buildCommand>
This command is placed before the JDT's builder. The launch configuration
itself has the following two items set.
<stringAttribute key="org.eclipse.ui.externaltools.ATTR_RUN_BUILD_KINDS"
value="full,incremental,clean"/>
<booleanAttribute
key="org.eclipse.ui.externaltools.ATTR_TRIGGERS_CONFIGURED" value="true"/>
So I would think that I could be guaranteed, for example, that when I
clean this project, that the external tools builder would be called and
would run my launch configuration.
The launch configuration, by the way, reads an input file and pulls
resources into the project from a remote server. These entries are
intended to usually be things that will be on your class path, but they're
not required to be.
So, with all that, my question is pretty much this: Should I be using a
launch configuration type or would it make more sense to create my own
Incremental project builder?
Thanks!
Richard
|
|
|
Powered by
FUDForum. Page generated in 0.03977 seconds
] 
Search
Help
Register
Login
Home
