Dominique Devienne wrote:
On 5/18/07, Steve Loughran <[EMAIL PROTECTED]> wrote:
OK. You've done what I've done, except with some stacking.
I had too, some of my builds had 3 or 4 levels, Makefile-style. Which
is not that surprising, since it was building mostly native stuff with
. I think it's
On 5/18/07, Steve Loughran <[EMAIL PROTECTED]> wrote:
OK. You've done what I've done, except with some stacking.
I had too, some of my builds had 3 or 4 levels, Makefile-style. Which
is not that surprising, since it was building mostly native stuff with
. I think it's essential to do the stacki
Dominique Devienne wrote:
On 5/18/07, Steve Loughran <[EMAIL PROTECTED]> wrote:
One question I have here, is : how should I present teh project name.
(a) with a . for example: kernel.init and kernel.common.init
-good for simple things, but imports can confuse it
(b) a / for example
On 5/18/07, Steve Loughran <[EMAIL PROTECTED]> wrote:
One question I have here, is : how should I present teh project name.
(a) with a . for example: kernel.init and kernel.common.init
-good for simple things, but imports can confuse it
(b) a / for example: kernel/init and kernel/c
I'm just coding up a new logger to make it easier to analyse big
projects built with subant. From the patched listeners.html:
BigProjectLogger
This logger is designed to make examining the logs of a big build easier,
especially those run under continuous integration tool
