Return-Path: Delivered-To: apmail-jakarta-commons-dev-archive@apache.org Received: (qmail 24098 invoked from network); 23 Oct 2002 02:22:13 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 23 Oct 2002 02:22:13 -0000 Received: (qmail 9438 invoked by uid 97); 23 Oct 2002 02:23:10 -0000 Delivered-To: qmlist-jakarta-archive-commons-dev@jakarta.apache.org Received: (qmail 9406 invoked by uid 97); 23 Oct 2002 02:23:09 -0000 Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Jakarta Commons Developers List" Reply-To: "Jakarta Commons Developers List" Delivered-To: mailing list commons-dev@jakarta.apache.org Received: (qmail 9392 invoked by uid 98); 23 Oct 2002 02:23:09 -0000 X-Antivirus: nagoya (v4218 created Aug 14 2002) From: "Adam Murdoch" To: "Jakarta Commons Developers List" Subject: RE: gumpifying vfs Date: Wed, 23 Oct 2002 12:20:41 +1000 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) In-reply-to: X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300 Importance: Normal X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N > -----Original Message----- > From: dion@multitask.com.au [mailto:dion@multitask.com.au] > Sent: Wednesday, 23 October 2002 10:50 AM > To: Jakarta Commons Developers List > Subject: Re: gumpifying vfs > > > Adam, doesn't vfs use Maven? > > If so, how about just generating the ant and gump files so we can smooth > the process out of getting commons projects built by Gump. Ok, I've done this. There were a couple of tiny issues: The vfs tests have a post goal action on test:test-resources, that sets up a bunch of test data. The generated build.xml doesn't invoke this action (which is fair enough), so the tests fail. Which causes the build to fail. Simplest solution might be to rearrange the dependencies in the generated build.xml, so that the jar target depends on compile-tests, and dist depends on test. Rather than dist -> jar -> test -> compile-tests. Even better would be if the ant plugin knew that it shouldn't run the tests if there are custom actions hanging off the test goals. Or if it could somehow invoke those actions. Or provide some way for me to specify which tests are runnable from the ant script, and which are not. Also, with the generated gump.xml, it might be better if the from address in the nag email is someone a little closer related to the project (like, say, one of the developers), rather than the maven developers. > -- > dIon Gillard, Multitask Consulting > Work: http://www.multitask.com.au > Developers: http://adslgateway.multitask.com.au/developers > > > Stefan Bodewig wrote on 23/10/2002 12:02:50 AM: > > > On Tue, 22 Oct 2002, Adam Murdoch wrote: > > > > > Anyone know how I get the vfs component included in the nightly gump > > > runs? > > > > Ask and thou shalt be given ;-) > > > > Where is the build file, which target should we call, which > > dependencies are there, what's the name/location of the resulting jar > > and javadocs? > > > > Is that all, hmm, yes, think so. > > > > Stefan > > > > -- > > To unsubscribe, e-mail: > > > For additional commands, e-mail: > > > > > > ForwardSourceID:NT00083F42 > > -- > To unsubscribe, e-mail: For additional commands, e-mail: -- To unsubscribe, e-mail: For additional commands, e-mail: