public inbox for mauve-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Christian Thalinger <twisti@complang.tuwien.ac.at>
To: mauve-discuss ml <mauve-discuss@sourceware.org>
Subject: build directory support
Date: Wed, 21 May 2008 15:21:00 -0000	[thread overview]
Message-ID: <1211383268.24194.59.camel@imac523d.theobroma-systems.com> (raw)

Hi!

I've just commited a bunch of patches to add the missing Uses tags for
various packages.  This is a preparation for the real patch that adds
build directory support.

I decided to implement/fix this because I didn't want to copy a handfull
of Mauve sources around to test it, but rather use one checkout on a NFS
share.

Currently it works very well (locally) and the Harness only compiles
sources when there is no corresponding classfile or the sourcefile is
newer than the classfile (inner classes are not checked).

There's only one problem left: different files some tests depend on.
Some testlets, like
gnu/testlet/java/beans/SimpleBeanInfo/loadImage.java, require the file
to be relative to the classfile location, so we need a way to copy these
files to the build directory.

On IRC I talked to Mark and Andrew and we concluded that a new tag would
be the best solution.  Like:

// Files: testImage1.gif

This tag would then copy the file from the source directory to the build
directory, if it does not already exist.

I'd like to commit my changes ASAP because I'm not sure I can find all
broken testlets.

- twisti

                 reply	other threads:[~2008-05-21 15:21 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1211383268.24194.59.camel@imac523d.theobroma-systems.com \
    --to=twisti@complang.tuwien.ac.at \
    --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).