Community
Participate
Working Groups
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.
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 ***