From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5962 invoked by alias); 16 Apr 2004 09:31:31 -0000 Mailing-List: contact mauve-discuss-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: mauve-discuss-owner@sources.redhat.com Received: (qmail 5939 invoked from network); 16 Apr 2004 09:31:30 -0000 Received: from unknown (HELO cuddles.cambridge.redhat.com) (81.96.64.123) by sources.redhat.com with SMTP; 16 Apr 2004 09:31:30 -0000 Received: from redhat.com (localhost.localdomain [127.0.0.1]) by cuddles.cambridge.redhat.com (8.12.8/8.12.8) with ESMTP id i3G9U2P0022583; Fri, 16 Apr 2004 10:30:12 +0100 Received: (from aph@localhost) by redhat.com (8.12.8/8.12.8/Submit) id i3G9U1dD022579; Fri, 16 Apr 2004 10:30:01 +0100 From: Andrew Haley MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16511.42905.101387.569375@cuddles.cambridge.redhat.com> Date: Fri, 16 Apr 2004 09:31:00 -0000 To: Mark Wielaard Cc: Thomas Zander , mauve-discuss@sources.redhat.com Subject: Re: Some issues.. In-Reply-To: <1082067738.1986.49.camel@elsschot.wildebeest.org> References: <200404031504.41093.zander@javalobby.org> <16494.47358.415834.600012@cuddles.cambridge.redhat.com> <200404031540.39350.zander@javalobby.org> <16494.56084.958410.241061@cuddles.cambridge.redhat.com> <1082067738.1986.49.camel@elsschot.wildebeest.org> X-SW-Source: 2004-q2/txt/msg00039.txt.bz2 Mark Wielaard writes: > Hi, > > On Sat, 2004-04-03 at 17:41, Andrew Haley wrote: > > Thomas Zander writes: > > > Second; I found at least one directory that contains java files without a > > > package; leading it to be uncompilable (due to duplicate class names) > > > I found: > > > gnu/testlet/BinaryCompatibility/altered/ > > > Should those have package lines?? > > > > No. This package comes with a script that does the building and > > copies some files around. I suppose you could create a Ant version of > > this script. > > Which script is this? Err, the one in the BinaryCompatibility directory... It's called `foo', of course! :-) > Is it documented? Yeah, right. > Might it be a good idea to add these tests to a separate module > like the visual tester and the verifier tests since they are > actually different from the rest of the mauve core library tests? Can you please be a little more specific about this? Andrew.