Return-Path: Delivered-To: apmail-xml-axis-dev-archive@xml.apache.org Received: (qmail 99131 invoked by uid 500); 27 Nov 2002 19:51:18 -0000 Mailing-List: contact axis-dev-help@xml.apache.org; run by ezmlm Precedence: bulk Reply-To: axis-dev@xml.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list axis-dev@xml.apache.org Received: (qmail 99122 invoked from network); 27 Nov 2002 19:51:18 -0000 Message-ID: <004d01c2964e$50267bb0$0202a8c0@zermatt> From: "Steve Loughran" To: References: <3DE51F18.EA149177@sonicsoftware.com> Subject: Re: Today's IRC log Date: Wed, 27 Nov 2002 11:50:45 -0800 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.2720.3000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N ----- Original Message ----- From: "David Chappell" To: Sent: Wednesday, November 27, 2002 11:38 Subject: Re: Today's IRC log > > In the meantime, I'm wondering if any of you ant-meisters can tell me if > there is a way to at least get the test code checked in, but excluded > from the test execution. The current behavior seems to be that its mere > existence in the directory structure causes the test to get executed. > If the test fails, the whole build fails (that in itself is an issue). 1. Have a condition like jms.server.present that is set if there is a server 2. in a patternset, include the jms build file only if that condition is set, and include that in the compile 3. Or, pass the flag down to junit and extract it in the test case and only run the test if the server is present. When I commit the offline stuff you'll see these techniques in action;