Mailing-List: contact dev-help@harmony.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@harmony.apache.org
Received-SPF: pass (herse.apache.org: domain of wuyuehao@gmail.com designates
 66.249.82.224 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=J2N9FKswFKn8NBwu+0beqNXdu1MazRvNceSidNWgymMFaoULlkIWu+SHdVtc9oc3ZmwZ6kG1YsbH8c01eZOid7rWKeox7O9/B3erG4JUzDllsWUo/XM1rh7vCdUjqz48HY5sloud80sXlp4jR/QBPSKjXlJaXtVMYTzGrNsnNG8=
Message-ID: <211709bc0701110700l6995ffadl64f9fa382167a92d@mail.gmail.com>
Date: Thu, 11 Jan 2007 23:00:09 +0800
From: "Tony Wu" <wuyuehao@gmail.com>
To: dev@harmony.apache.org
Subject: Re: Re: [classlib][pack200] Updated project and build
In-Reply-To: <636fd28e0701101302q5c8b0895t5288d76fe5aef340@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <636fd28e0701091656r75fdcf07y2a9b579803a94c27@mail.gmail.com>
	 <45A4E30D.5000400@gmail.com>
	 <636fd28e0701101302q5c8b0895t5288d76fe5aef340@mail.gmail.com>

how about refer your jar file as a dependency, like yoko does?
when you need update the file, you do not have to submit a new one but
create a patch for modified properties.xml

On 1/11/07, Alex Blewitt <alex.blewitt@gmail.com> wrote:
> On 10/01/07, Tim Ellison <t.p.ellison@gmail.com> wrote:
> > Alex Blewitt wrote:
> > >
> > > One thing I did notice was that when I was submitting a Jar (stubs of
> > > 1.5 required classes outside of a 1.5 system) the svn diff didn't
> > > create the contents. The patch just read:
> >
> > Attaching the file to the JIRA, or zipping a bunch of files to be added
> > together, has been the way to date.  Some kind folk even provide the svn
> > add/move script or a set of instructions for applying it.
>
> Yeah, that's what I did in the end. I was just surprised that the svn
> diff didn't actually do a diff of binary files; that almost certainly
> explains some of the earlier failures in applying of the patches; I
> was assuming the patch contained the binary files, whereas it didn't.
>
> It also means that when adding binary files (e.g. the test data for
> the packed Jars) I need to be careful that I remember to add any
> binary files that I've changed. :-(
>
> Alex.
>


-- 
Tony Wu
China Software Development Lab, IBM