public inbox for mauve-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Raif S. Naffah" <raif@swiftdsl.com.au>
To: Mark Wielaard <mark@klomp.org>
Cc: mauve-discuss@sourceware.org
Subject: Re: patch to improve use with Eclipse
Date: Thu, 22 Dec 2005 11:03:00 -0000	[thread overview]
Message-ID: <200512222204.46970.raif@swiftdsl.com.au> (raw)
In-Reply-To: <1135177669.7227.75.camel@localhost.localdomain>

[-- Attachment #1: Type: text/plain, Size: 1604 bytes --]

hello Mark,

On Thursday 22 December 2005 02:07, Mark Wielaard wrote:
> Hi Raif,
>
> On Thu, 2005-12-22 at 00:39 +1100, Raif S. Naffah wrote:
> > pls. find attached a patch to improve the use of Mauve with
> > (Native) Eclipse.
>
> Could you give some guidance for a newbie like me?
> I installed this and now I have under Run->External Tools a new item
> MauveBatchRun. If I select that (after following almost everything in
> http://developer.classpath.org/mediation/ClasspathHackingWithEclipse)
> it seems to configure mauve and then says:
> [Console output redirected to
> file:/home/mark/workspace/mauve/mauve.out]
>
> But there is nothing in that file.

i just checked out Mauve, including this Runner, restarted Eclipse and 
tried it and it (still) works!

i did see the symptoms you're describing when (a) the built VM had 
problems; (b) the VM was not configured properly; e.g. not picking up 
the correct Classpath classes; and/or (c) the environment variables 
--defined in this Runner-- are not being picked up.  in these cases, 
the Mauve scripts would run, but no test class is selected for the 
"runner" script to run them.

the best way to debug why nothing is being written to mauve.out is to 
add some 'echo ' statements in batch_run, choose-classes and runner.  
also, on line 119 of the batch_run script, invert 2 and 1 so you can 
see the stderr output on the Eclipse console.

finally, did you create the symbolic link to mauve-classpath keys file?


>
> I did commit it so others can play more easily with it though.

thanks + cheers;
rsn

[-- Attachment #2: Type: application/pgp-signature, Size: 216 bytes --]

  parent reply	other threads:[~2005-12-22 11:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-21 13:38 Raif S. Naffah
2005-12-21 15:07 ` Mark Wielaard
2005-12-21 23:46   ` Mark Wielaard
2005-12-22 11:03   ` Raif S. Naffah [this message]
2005-12-22 21:32     ` Mark Wielaard
2005-12-23  7:46       ` Raif S. Naffah

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200512222204.46970.raif@swiftdsl.com.au \
    --to=raif@swiftdsl.com.au \
    --cc=mark@klomp.org \
    --cc=mauve-discuss@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).