Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 96043

Summary:	[launching] [builders] External Builders defined in a project should be able to default to project directory
Product:	[Eclipse Project] Platform	Reporter:	MG <java97301>
Component:	Ant	Assignee:	Platform-Ant-Inbox <platform-ant-inbox>
Status:	RESOLVED WONTFIX	QA Contact:
Severity:	enhancement
Priority:	P3	CC:	Michael_Rennie
Version:	3.1	Keywords:	helpwanted
Target Milestone:	---
Hardware:	PC
OS:	Windows 2000
Whiteboard:

Description MG

2005-05-19 19:10:00 EDT

I have an external builder that exists within a project.  Now it would be nice
to make it such this builder referenced resources from within the project by
default, allowing anyone else using the project to have this builder and have it
project-name independant.

e31m7

Comment 1 MG

2005-05-19 19:11:46 EDT

You can see the two references to myproject-name below in the ant external
builder definition.  Also is there a way if I have the information below in a
file that I could import that into my project?  I can't seem to find a way. 
Thank you !

<?xml version="1.0" encoding="UTF-8"?>
<launchConfiguration type="org.eclipse.ant.AntBuilderLaunchConfigurationType">
<booleanAttribute key="org.eclipse.debug.ui.ATTR_LAUNCH_IN_BACKGROUND"
value="false"/>
<booleanAttribute key="org.eclipse.ant.ui.DEFAULT_VM_INSTALL" value="false"/>
<stringAttribute key="org.eclipse.ant.ui.ATTR_ANT_MANUAL_TARGETS" value="init,"/>
<stringAttribute key="org.eclipse.ui.externaltools.ATTR_RUN_BUILD_KINDS"
value="full,incremental,"/>
<booleanAttribute key="org.eclipse.ant.ui.ATTR_TARGETS_UPDATED" value="true"/>
<stringAttribute key="org.eclipse.ui.externaltools.ATTR_WORKING_DIRECTORY"
value="${workspace_loc:/myproject-name}"/>
<stringAttribute key="org.eclipse.ui.externaltools.ATTR_LOCATION"
value="${workspace_loc:/myproject-name/build/build.xml}"/>
<booleanAttribute key="org.eclipse.ui.externaltools.ATTR_TRIGGERS_CONFIGURED"
value="true"/>
<booleanAttribute key="org.eclipse.debug.core.appendEnvironmentVariables"
value="true"/>
<stringAttribute key="org.eclipse.jdt.launching.CLASSPATH_PROVIDER"
value="org.eclipse.ant.ui.AntClasspathProvider"/>
</launchConfiguration>

Comment 2 Darin Swanson

2005-05-20 11:55:56 EDT

Thank you for the bug report.
There is no import support and none is planned for 3.1
Support for name relative launch configs will not happen for 3.1 either

Deferred to post 3.1

Comment 3 Darin Swanson

2006-01-10 18:55:59 EST

*** Bug 123352 has been marked as a duplicate of this bug. ***

Comment 4 MG

2006-07-07 20:06:03 EDT

Now that 3.2 is out are there plans to address the name relative launch configs?

Comment 5 Darin Swanson

2006-07-07 20:09:25 EDT

We are still in the stages of planning for 3.3.
Thanks for the ping.

Comment 6 MG

2007-10-23 14:11:35 EDT

Now that 3.3 is out any plans for this in 3.4?

(In reply to comment #5)
> We are still in the stages of planning for 3.3.
> Thanks for the ping.
>

Comment 7 Darin Swanson

2007-10-23 15:53:41 EDT

Currently no enhancements are planned for the Eclipse platform Ant integration.
That said, patches will be reviewed and considered

Comment 8 Michael Rennie

2011-06-06 16:51:01 EDT

There are no plans to implement this.

Marking as wontfix, we can reopen if a patch is provided.