Alex Boisvert wrote:
It works for a single buildfile only. Why not use a single buildfile? If
the projects are related, it's easier to have a single buildfile.
about single buildfile: when there are many projects, and therefore,
many committers, a single buildfile becomes a headache as the different
commits create conflicts (esp. if done in editors with different
indentation settings) and require merging. basically, it's the same
reason as to separate code into individual files, sure it is easier to
have it all in one place, but the lack of modularity is a boomerang.
ittay
alex
On Sun, Mar 15, 2009 at 10:28 PM, Sakari Isoniemi <[email protected]
wrote:
OK, but
Does the notation
project("A").project("B").project("C")
really work if we have a buildfile in DIRECTORIES A and C ?
Or do we have to have a buldfile also in directory B, from where
buildfile in directory C is called ?
2009/3/16 Alex Boisvert <[email protected]>
It depends on how you define your projects... generally you'd refer to
sub-project with the colon notation.
project("A:B:C") # This is project A -> sub-project B -> sub-project C
since it's shorter, although you can also use the longer form:
project("A").project("B").project("C")
alex
On Sun, Mar 15, 2009 at 12:59 PM, Sakari Isoniemi <
[email protected]
wrote:
How to call a projects task, that is in subdirectory ?
For ex. the current directory is A, where is a buildfile.
How from this buildfile is called project/task, which buildfile is
in directory A/B/C ?
The notation
compile.with projects('B\C\projX')
won't work
--
Tikal <http://www.tikalk.com>
Tikal Project <http://tikal.sourceforge.net>
