From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13191 invoked by alias); 8 Sep 2005 16:44:28 -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 12972 invoked by uid 22791); 8 Sep 2005 16:44:17 -0000 Received: from mx1.redhat.com (HELO mx1.redhat.com) (66.187.233.31) by sourceware.org (qpsmtpd/0.30-dev) with ESMTP; Thu, 08 Sep 2005 16:44:17 +0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.12.11/8.12.11) with ESMTP id j88GiF1J006069 for ; Thu, 8 Sep 2005 12:44:16 -0400 Received: from opsy.redhat.com (vpn50-46.rdu.redhat.com [172.16.50.46]) by int-mx1.corp.redhat.com (8.11.6/8.11.6) with ESMTP id j88GiFV30079; Thu, 8 Sep 2005 12:44:15 -0400 Received: by opsy.redhat.com (Postfix, from userid 500) id 428772DD4A0; Thu, 8 Sep 2005 10:39:27 -0600 (MDT) To: GNU Classpath Project Cc: Mauve News Group Subject: testing with eclipse From: Tom Tromey Reply-To: tromey@redhat.com X-Attribution: Tom Date: Thu, 08 Sep 2005 16:44:00 -0000 Message-ID: User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3.50 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-SW-Source: 2005-q3/txt/msg00019.txt.bz2 I checked in some eclipse build infrastructure to the wonka module in mauve, including a launch configuration. Now you should be able to very easily test classpath changes using the visual tester without leaving eclipse. It is literally a push-button operation. To do this, first you have to set up an eclipse workspace containing classpath and jamvm; follow the instructions I posted a short while ago. (At the moment this is not totally trivial as it requires a jamvm patch.) Then, check out the wonka module from mauve. When this is done, you should see a launch configuration called "WonkaVisualTestEngine" (I have only done this stuff in my workspace, I'm not totally sure it will automatically show up after a checkout.) If you run this launch config, the test engine will start up. It is set up to always load all the tests; however is it very easy to add your own launch configurations. (Please don't modify the shared one unless your changes are appropriate for everybody.) Eclipse puts your most recently used launch configuration at the top of the list. So once you've run this once, testing classpath changes works like this: * Modify Classpath sources * Save the change (eclipse automatically recompiles, it is nearly instantaneous for most changes). * Click the button to run the launch configuration * Repeat I'll add a simple way to run all of mauve as well. (We could make things even easier in some ways, especially for mauve, but that would require real programming. Maybe someone would like to volunteer :-) Tom