Return-Path: Mailing-List: contact user-help@ant.apache.org; run by ezmlm Delivered-To: mailing list user@ant.apache.org Received: (qmail 56499 invoked from network); 27 May 2003 15:14:55 -0000 Received: from mail02.frontiercorp.com (HELO snnymail04.east.frontiercorp.com) (66.133.172.50) by daedalus.apache.org with SMTP; 27 May 2003 15:14:55 -0000 Received: from snnymail04.east.frontiercorp.com (localhost [127.0.0.1]) by snnymail04.east.frontiercorp.com (Switch-3.0.4/Switch-3.0.0) with ESMTP id h4RFCSUT020085 for ; Tue, 27 May 2003 11:12:28 -0400 (EDT) Received: from nyrofcs2kexch05.corp.pvt (nyrofcs2kexch05.corp.pvt [10.160.64.244]) by snnymail04.east.frontiercorp.com (Switch-3.0.4/Switch-3.0.0) with ESMTP id h4RFBvUW019952 for ; Tue, 27 May 2003 11:11:59 -0400 (EDT) Received: by nyrofcs2kexch05.corp.pvt with Internet Mail Service (5.5.2654.89) id ; Tue, 27 May 2003 11:10:24 -0400 Message-ID: From: "Finn, Michael" To: "'Ant Users List'" Subject: RE: do we have jarsigner tar in ant? Date: Tue, 27 May 2003 11:10:23 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2654.89) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C32462.0CE22A5F" X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N ------_=_NextPart_001_01C32462.0CE22A5F Content-Type: text/plain; charset="iso-8859-1" signjar doesn't give you what you need? -----Original Message----- From: Verma, Nitin (GECP, OTHER, 529706) [mailto:NITIN.VERMA@APPL.GE.COM] Sent: Tuesday, May 27, 2003 11:11 AM To: Ant Users List Subject: do we have jarsigner tar in ant? Not able to find any task like this on ant.apache.org! Help! $ jarsigner Usage: jarsigner [options] jar-file alias jarsigner -verify [options] jar-file [-keystore ] keystore location [-storepass ] password for keystore integrity [-storetype ] keystore type [-keypass ] password for private key (if different) [-sigfile ] name of .SF/.DSA file [-signedjar ] name of signed JAR file [-verify] verify a signed JAR file [-verbose] verbose output when signing/verifying [-certs] display certificates when verbose and verifying [-internalsf] include the .SF file inside the signature block [-sectionsonly] don't compute hash of entire manifest [-provider] name of cryptographic service provider's master class file ... ------_=_NextPart_001_01C32462.0CE22A5F--