Right now includeFlat takes a list of project names, and assumes ../a_proj
for the directory location, and uses the project name of a_proj.

It would be extremely powerful to allow for a mapping of project names to
actual directory locations.

['a_proj':'../../../elsewhere', 'b_proj':'../../../b_proj',
'c_proj':'../c_proj_old', 'd_proj':'../d_proj']

['a_proj':'../a_proj', 'b_proj':'../../../b_proj', 'c_proj':'../c_proj_old',
'd_proj':'../../../other_proj', 'e_proj':'e_proj',
'f_proj':'/some/absolute/path/elsewhere/f_proj',
'g_proj':'d:/other/drive/other_proj']

a_proj would be identical to what includeFlat does now
b_proj would allow for the project to live someplace different from just
right next to the current project
c_proj would be identical to what includeFlat does now, but allows aliasing
of the project name
d_proj would allow for the project to live someplace different from just
right next to the current project and allows aliasing of the project name
e_proj would produce the same result as using include (so technically
include and includeFlat taking lists could just defer their functions to
includeFlat taking a map)
f_proj would allow an absolute path to the named project
g_proj would allow for an absolute path to an aliased project

What's interesting is what includeFlat '../other_proj' does now in the
latest gradle0.9 snapshot.

It actually finds the directory two levels above (assuming it exists) and
names the project '../other_proj' so that it looks like project
':../other_proj' when printed out.

Having the above kind of control would greatly simplify a dependent build
I'm trying to construct that has directory structures that cannot (easily)
co-exist directly next to each other.

-Spencer
-- 
View this message in context: 
http://old.nabble.com/includeFlat-possibly-could-be-overloaded-to-accept-a-map-tp27536529p27536529.html
Sent from the gradle-dev mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


Reply via email to