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 <[EMAIL PROTECTED]> wrote:
On 10/01/07, Tim Ellison <[EMAIL PROTECTED]> 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

Reply via email to