Return-Path: Delivered-To: apmail-jakarta-tomcat-dev-archive@jakarta.apache.org Received: (qmail 39637 invoked by uid 500); 21 Sep 2001 07:38:40 -0000 Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: tomcat-dev@jakarta.apache.org Delivered-To: mailing list tomcat-dev@jakarta.apache.org Received: (qmail 39628 invoked from network); 21 Sep 2001 07:38:40 -0000 Message-ID: <062901c14270$f3f64d20$82deb018@intalio.com> From: "Remy Maucherat" To: References: <1001054097.3baadf91b5bf5@www.mhsoftware.com> Subject: Re: New Ant Target for TC4 Date: Fri, 21 Sep 2001 00:42:20 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N > 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