public inbox for
 help / color / mirror / Atom feed
From: Tom Tromey <>
Subject: [Per Bothner <>] Re: forwarded message from Adam Heath
Date: Thu, 25 Oct 2001 18:26:00 -0000	[thread overview]
Message-ID: <> (raw)

This is undoubtedly the cause of the jar problem we were seeing.
fastjar's `u' option doesn't work.

------- Start of forwarded message -------
Message-ID: <>
Date: Thu, 25 Oct 2001 16:34:12 -0700
From: Per Bothner <>
MIME-Version: 1.0
Subject: Re: forwarded message from Adam Heath
References: <15320.39495.965333.183669@gargle.gargle.HOWL>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=us-ascii; format=flowed

Matthias Klose wrote:

>Not only does fastjar obliterate existing contents in a jar when updating,
>but, it appears it can also corrupt the file.
Yes, I ran into the same problem.  Basically the implementation of 'u'
is pretty much not there.  I looked at trying to fix it, but decided I 
have time.  Until somebody fixes it, we should change fastjar to exit 
with an
error on 'u'.

The first question is whether fastjar should try to update
in place or create a temporary file and copy it over.  The former is faster,
especially when just adding files, and is less liable to run out of disk 
However, it is tricky when files are replaced that are not at the end. 
 In that
case I guess the solution is to read the archive members that need to be 
into main memory.

Then it is just a small matter of programming ...

------- End of forwarded message -------

             reply	other threads:[~2001-10-25 18:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-25 18:26 Tom Tromey [this message]
2001-10-25 21:32 ` Alexandre Petit-Bianco

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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).