[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [platform-ant-dev] Launching external tools with launch configs?
|
From a technical point of view the operations are similar, but from a
user's perspective the operations are different. Launch configurations are
used for running/testing the stuff that the user is actually developing --
the "product" that the user is creating using the IDE. External tools, on
the other hand, are really extensions to the IDE itself. They generally
operate on the stuff that the user is directly developing. These tools
often aren't located in the workspace themselves, but instead they operate
on the contents of the workspace. In some cases they will be transparent
to the user (for example if they are scripts installed on the build path as
external tool builders). Another distinction is that it would not
generally be desirable or even feasible to launch external tools in debug
mode.
So yes, we did consider using launch configs, and that's some of the
reasoning behind our decision not to use them. It basically felt strange
to be using one mechanism for two very different user concepts -- even
though from a technology viewpoint they had some similar characteristics.
Jared Burns
<jared-eclipse@xxxxxxxx To: platform-ant-dev@xxxxxxxxxxx
m> cc:
Sent by: Subject: [platform-ant-dev] Launching external tools with
platform-ant-dev-admin@ launch configs?
eclipse.org
09/24/2002 03:07 PM
Please respond to
platform-ant-dev
It seems to me that the external tools framework is recreating a concept
that
already exists with launch configs.
I'm curious to know if the ant developers considered using the launch
configuration framework for ant/external tools. If so, can someone
summarize
why we opted to use a different solution? If not, what do people think of
migrating the external tools code to use launch configs?
Thanks,
- Jared
