Return-Path: 
 <cocoon-dev-return-17482-apmail-xml-cocoon-dev-archive=xml.apache.org@xml.apache.org>
Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org
Received: (qmail 63725 invoked by uid 500); 5 Oct 2001 14:39:28 -0000
Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:cocoon-dev-help@xml.apache.org>
list-unsubscribe: <mailto:cocoon-dev-unsubscribe@xml.apache.org>
list-post: <mailto:cocoon-dev@xml.apache.org>
Reply-To: cocoon-dev@xml.apache.org
Delivered-To: mailing list cocoon-dev@xml.apache.org
Received: (qmail 63707 invoked from network); 5 Oct 2001 14:39:28 -0000
Date: Sat, 6 Oct 2001 00:40:54 +1000
From: Jeff Turner <jeff@socialchange.net.au>
To: cocoon-dev@xml.apache.org
Subject: Re: [PATCH] Run-from-jar broken
Message-ID: <20011006004053.A13137@kermit.socialchange.net.au>
Mail-Followup-To: cocoon-dev@xml.apache.org
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20011005091224.A3581@renie.dyndns.org>
User-Agent: Mutt/1.3.19i
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

On Fri, Oct 05, 2001 at 09:12:24AM +0200, Martin Man wrote:
> hi jeff,
> 	patch applied on both branches, please crosscheck...

Thanks. All looks fine.

I'll look into creating a manifest automatically with <pathconvert> and
<echo file="src/Manifest.mf">. The current situation is very brittle, because
it's likely that people updating the jars will forget to update the manifest.

--Jeff
> 
> rgds,
> martin

---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org