public inbox for rhug-rhats@sourceware.org
 help / color / mirror / Atom feed
From: Anthony Green <green@redhat.com>
To: Gary Benson <gbenson@redhat.com>
Cc: rhug-rhats@sources.redhat.com
Subject: Re: rhug/xalan ChangeLog configure.in configure
Date: Tue, 09 Sep 2003 18:31:00 -0000	[thread overview]
Message-ID: <1063132286.21943.39.camel@escape> (raw)
In-Reply-To: <20030909084021.GA3382@redhat.com>

On Tue, 2003-09-09 at 01:40, Gary Benson wrote:
> Why is this necessary?  I couldn't find a single place in xalan where
> jakarta-regexp is referenced...

It's referenced in BCEL, which is used by Xalan.  The rhug build will,
under some conditions, put the BCEL source tree on the classpath.  
Hmm.. is the solution just to make sure that it uses the BCEL jar file
from the build tree?

AG

-- 
Anthony Green <green@redhat.com>
Red Hat, Inc.

  reply	other threads:[~2003-09-09 18:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20030908171322.32106.qmail@sources.redhat.com>
2003-09-09 16:32 ` Gary Benson
2003-09-09 18:31   ` Anthony Green [this message]
2003-09-11 15:43     ` Gary Benson
2003-09-11 16:05       ` Anthony Green
2003-09-11 16:09         ` Gary Benson

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=1063132286.21943.39.camel@escape \
    --to=green@redhat.com \
    --cc=gbenson@redhat.com \
    --cc=rhug-rhats@sources.redhat.com \
    /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).