Return-Path: Delivered-To: apmail-jakarta-ant-user-archive@jakarta.apache.org Received: (qmail 31698 invoked by uid 500); 20 Jul 2001 14:21:19 -0000 Mailing-List: contact ant-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: Reply-To: ant-user@jakarta.apache.org Delivered-To: mailing list ant-user@jakarta.apache.org Received: (qmail 31689 invoked from network); 20 Jul 2001 14:21:19 -0000 Content-Class: urn:content-classes:message Subject: RE: Jar task MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Date: Fri, 20 Jul 2001 15:20:52 +0100 Message-ID: X-MimeOLE: Produced By Microsoft Exchange V6.0.4712.0 X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Jar task Thread-Index: AcERJpMrgnJoh5MZRqusyZOUjqRQkwAAE1vA From: "Jon Skeet" To: X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N > I downloaded the 1.4alpha that was built last night, and used the > update=3D"true" flag. However, the problem is that I want to=20 > use jar with the update but also with the M option. The M does not create a=20 > manifest for the entries. Hmmm... not sure about that. As for *including* the manifest, I would have thought the manifest attribute of the jar task would be the way to go, rather than explicitly including the file. Might that be what you were after? I would imagine you don't need a basedir at all in this case, although I haven't tried it. Jon