public inbox for rhug-rhats@sourceware.org
 help / color / mirror / Atom feed
From: Anthony Green <green@redhat.com>
To: Christophe Roux <ch_roux@club-internet.fr>
Cc: rhug-rhats@sources.redhat.com
Subject: Re: Tomcat Manifest
Date: Mon, 02 Dec 2002 21:05:00 -0000	[thread overview]
Message-ID: <1038891978.4993.34.camel@escape> (raw)
In-Reply-To: <E18G0yI-0002UU-00@smarthost2.mail.easynet.fr>

On Sun, 2002-11-24 at 12:01, Christophe Roux wrote:
> I am asking :
> - do I need to configure a manifest.mf or a deployment descriptor in order to 
> have a correct installation ?
> - if so, is there a document on the web which could indicate haw to create 
> such a file ?
> - someone can explain simply how to do that?

I'm afraid I don't know the answer to any of these questions. 

Gary Benson is in the process of upgrading some of the rhug packages in
order to get Tomcat 4.* working.  Hopefully some more eyes on these
issues will help resolve them.

AG


      reply	other threads:[~2002-12-03  5:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-24  9:55 Christophe Roux
2002-12-02 21:05 ` Anthony Green [this message]

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=1038891978.4993.34.camel@escape \
    --to=green@redhat.com \
    --cc=ch_roux@club-internet.fr \
    --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).