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

Bug 108625

Summary:	mix between "buildDirectory" and "baseLocation" attributes of the "eclipse.buildScript" ant task ?
Product:	[Eclipse Project] PDE	Reporter:	Francois Granade <francois>
Component:	Build	Assignee:	Andrew Niefer <aniefer>
Status:	RESOLVED INVALID	QA Contact:
Severity:	minor
Priority:	P3	CC:	aniefer
Version:	3.1
Target Milestone:	---
Hardware:	All
OS:	All
Whiteboard:

Description Francois Granade

2005-09-01 15:35:37 EDT

I found that in some cases, "buildDirectory" and "baseLocation" can be
interchangeable. I have one feature with one plugin that only has dependencies
on the platform, and whether I run:
  <eclipse.buildScript elements="feature@org.nexb.eclipse.myfeature"
     baseLocation="/Applications/easyeclipse 1.0"
     buildDirectory="/Users/francois/build"/>
or:
  <eclipse.buildScript elements="feature@org.nexb.eclipse.myfeature"
     buildDirectory="/Applications/easyeclipse 1.0"
     baseLocation="/Users/francois/build"/>

I get the same results.

I think that in the second case, there should be an error like this:
"Feature org.nexb.eclipse.myfeature not found in build directory
/Application/easyeclipse 1.0"

this is cosmetic, but may be the sign of a bigger problem underneath

Comment 1 Francois Granade

2005-09-01 17:25:01 EDT

os is "all", not "macos"

Comment 2 Andrew Niefer

2007-10-30 15:02:42 EDT

baseLocation and buildDirectory are the same except for the following

1) platform.xml and links directories are consulted in the baseLocation and not in the buildDirectory
2) buildDirectory is where the generated content goes.

They are only interchangeable if you don't care about poluting your baseLocation with generated content and if you are using the platform.xml and links functionality.