Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 123352 - The external builder option should be defaulted to the project where that external builder is defined.
Summary: The external builder option should be defaulted to the project where that ext...
Status: RESOLVED DUPLICATE of bug 96043
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Ant (show other bugs)
Version: 3.2   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform-Ant-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-01-10 18:34 EST by MG CLA
Modified: 2006-01-10 18:55 EST (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description MG CLA 2006-01-10 18:34:05 EST
Currently an ant external builder has the following properties.

<stringAttribute key="org.eclipse.ui.externaltools.ATTR_WORKING_DIRECTORY" value="${workspace_loc:/yourproject}"/>
<stringAttribute key="org.eclipse.ui.externaltools.ATTR_LOCATION" value="${workspace_loc:/yourproject/build/build.xml}"/>

In a large development team where people have different names for their workspaces having an external builder automatically defined and ready on a cvs update is impossible because the external builder file requires the workspace name even though the external builder configuration is included in the project workspace and should be able to figure out it's own project name.
Comment 1 Darin Swanson CLA 2006-01-10 18:55:59 EST
The workspace location is not specified but is a variable that is defined by each workspace. The Eclipse Ant development shares many external tool builders.

Do you mean people have have checked out the projects under different names?

I see this as a duplicate of the other bug you file...bug 96043.

Without community patches this support will not occur for 3.2



*** This bug has been marked as a duplicate of 96043 ***