New Ant Target for TC4

[Christopher Cain <cc...@mhsoftware.com>]

First of all, Remy, great work on the new build stuff. I particularly like the 
output at the beginning, where it reports which jars it found.

It's so useful, in fact, that I think it deserves its own target for several 
reasons ("detect" maybe?). First, it scrolls offscreen really quickly, and it's 
hard to scroll back up during a build. Second, it would sometimes be nice to 
see what is getting detecting without actually doing a build (if you are 
setting up a new development environment from scratch, for example). Also, it 
would be a great debugging tool for answering user build questions, since one 
could have them simply run the "detection" target and verify that everything is 
set up right.

Thoughts?

- Christopher

/**
 * Pleurez, pleurez, mes yeux, et fondez vous en eau!
 * La moitié de ma vie a mis l'autre au tombeau.
 *    ---Corneille
 */

Re: New Ant Target for TC4

[Remy Maucherat <rm...@home.com>]

> First of all, Remy, great work on the new build stuff. I particularly like
the
> output at the beginning, where it reports which jars it found.

Thanks, Chritopher.

> It's so useful, in fact, that I think it deserves its own target for
several
> reasons ("detect" maybe?).

Ok, I'll do that. 'detect' looks fine to me. It's not exposed by the top
level build script at the moment, but I'll add that.

> First, it scrolls offscreen really quickly, and it's
> hard to scroll back up during a build. Second, it would sometimes be nice
to
> see what is getting detecting without actually doing a build (if you are
> setting up a new development environment from scratch, for example). Also,
it
> would be a great debugging tool for answering user build questions, since
one
> could have them simply run the "detection" target and verify that
everything is
> set up right.

Remy