[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [platform-ant-dev] Copying existing configs to use as project builders
|
I second the unreasonability. I don't know the technical reasons behind it
however. The copy proposal might work as a starting point but perhaps the
near future should include referencing? If that is the case, beware of
adding API extension points you will regret later.
Jeff
"Darin Wright"
<Darin_Wright@xxxxxxx> To: platform-ant-dev@xxxxxxxxxxx
Sent by: cc:
platform-ant-dev-admin@ Subject: Re: [platform-ant-dev] Copying existing
eclipse.org configs to use as project builders
12/03/2002 10:29 PM
Please respond to
platform-ant-dev
This seems reasonable. I think it is unfortunate that we need to do this
(I'd still like to be able to simply use the "reference" technique).
However, with our current story, we require such infrastructure.
Darin
Jared Burns
<jared-eclipse@xxxxxxxxx> To:
Sent by: platform-ant-dev@xxxxxxxxxxx
platform-ant-dev-admin@eclip cc:
se.org Subject: [platform-ant-dev]
Copying existing configs to use as project
builders
12/03/2002 04:15 PM
Please respond to
platform-ant-dev
Bug 16574 (<http://bugs.eclipse.org/bugs/show_bug.cgi?id=16574>) covers a
feature we'd like to add whereby the user would be able to add an existing
launch configuration as an external tool project builder.
Adding an existing config ("by reference") is not technically feasible, but
we'd like to let the user copy ("by value") an existing config to be used
as
a project builder.
So we need a way to take a config of the type that shows up in the launch
config dialog and create a new "builder config" of the appropriate type.
For example, if the user wants to copy an Ant config to use as a project
builder, we need to take a config of type
"org.eclipse.ant.AntLaunchConfigurationType" and copy the attributes into a
new config of type "org.eclipse.ant.AntBuilderLaunchConfigurationType".
The only decent way I can think to do this is to create an extension point
that would allow external tool writers (like us) to explicitly state what
builder config type should be used when copying a normal config.
Extensions would look something like so:
<extension point
="org.eclipse.ui.externaltools.configurationDuplicationMap">
<configurationMap
type="org.eclipse.ant.AntLaunchConfigurationType"
builderType="org.eclipse.ant.AntBuilderLaunchConfigurationType">
</configurationMap>
<configurationMap
type="org.eclipse.ui.externaltools.ProgramLaunchConfigType"
builderType
="org.eclipse.ui.externaltools.ProgramBuilderLaunchConfigType">
</configurationMap>
</extension>
Good/bad/ugly?
- Jared
_______________________________________________
platform-ant-dev mailing list
platform-ant-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/platform-ant-dev
