From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23966 invoked by alias); 4 Aug 2003 19:15:31 -0000 Mailing-List: contact eclipse-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: eclipse-owner@sources.redhat.com Received: (qmail 23873 invoked from network); 4 Aug 2003 19:15:30 -0000 Date: Mon, 04 Aug 2003 19:15:00 -0000 Subject: Re: good work, JUnit help Content-Type: text/plain; charset=US-ASCII; format=flowed Mime-Version: 1.0 (Apple Message framework v552) Cc: eclipse@sources.redhat.com To: tromey@redhat.com From: Jonathan LaCour In-Reply-To: <87znipl0gu.fsf@fleche.redhat.com> Message-Id: <01F24A9C-C6B0-11D7-9F33-00039382A69A@skinnee.net> Content-Transfer-Encoding: 7bit X-Mailer: Apple Mail (2.552) X-SW-Source: 2003-q3/txt/msg00021.txt.bz2 Tom, > Could you post the full stack trace? Usually it ends up in > workspace/.metadata/.log. That might be useful. I looked in the workspace/.metadata directory, and found no such file ".log". The error message doesn't go to the "console" that I am running eclipse from, but actually into the "console" view inside Eclipse. So, there actually isn't any error printed to the .log file I don't believe. I have temporarily reverted back to the old version of Eclipse so that I can get some work done, otherwise I would do some further debugging. No time for that at work, you know =) > Anyway, an entry in the RH bugzilla would be useful. Something like > this has a pretty good chance of actually being fixed. I would be more than happy to put such an entry in, but some guidance on how to do so would be helpful. You might be able to get more information than I if you tried running a unit test yourself. Thanks for the hint! Great job thus far. - Jon