From open-jpa-dev-return-2307-apmail-incubator-open-jpa-dev-archive=incubator.apache.org@incubator.apache.org Wed Feb 21 18:26:14 2007 Return-Path: Delivered-To: apmail-incubator-open-jpa-dev-archive@locus.apache.org Received: (qmail 26248 invoked from network); 21 Feb 2007 18:26:14 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 21 Feb 2007 18:26:14 -0000 Received: (qmail 38588 invoked by uid 500); 21 Feb 2007 18:26:22 -0000 Delivered-To: apmail-incubator-open-jpa-dev-archive@incubator.apache.org Received: (qmail 38563 invoked by uid 500); 21 Feb 2007 18:26:22 -0000 Mailing-List: contact open-jpa-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: open-jpa-dev@incubator.apache.org Delivered-To: mailing list open-jpa-dev@incubator.apache.org Received: (qmail 38554 invoked by uid 99); 21 Feb 2007 18:26:22 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 21 Feb 2007 10:26:22 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of ppoddar@bea.com designates 66.248.192.22 as permitted sender) Received: from [66.248.192.22] (HELO usremg02.bea.com) (66.248.192.22) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 21 Feb 2007 10:26:11 -0800 Received: from usremr02.bea.com (mailrelay.bea.com [10.160.29.92]) by usremg02.bea.com (Switch-3.2.2/Switch-3.2.2) with ESMTP id l1LIPnwT027574 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Wed, 21 Feb 2007 10:25:50 -0800 Received: from repbex01.amer.bea.com (repbex01.bea.com [10.160.26.98]) by usremr02.bea.com (Switch-3.2.2/Switch-3.2.2) with ESMTP id l1LIPPDu007702 for ; Wed, 21 Feb 2007 10:25:48 -0800 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: Can enhancer operate on jar files? Date: Wed, 21 Feb 2007 10:25:24 -0800 Message-ID: <5C219175D559A64D8C2CC65E41D36856C8AE11@repbex01.amer.bea.com> In-Reply-To: <636222B6-1181-4E2B-ADDC-86C40F19D044@SUN.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Can enhancer operate on jar files? Thread-Index: AcdV37tqJ+qjPe1ERt+p+cNqS4BzxAABSirg References: <77E7952D-60CD-4D99-B029-93827D7DC2FB@iq80.com> <5C219175D559A64D8C2CC65E41D36856C8AA85@repbex01.amer.bea.com> <91772E93-7B69-4E05-8952-BBEA765914C3@iq80.com> <636222B6-1181-4E2B-ADDC-86C40F19D044@SUN.com> From: "Pinaki Poddar" To: X-PMX-Version: 4.7.1.128075, Antispam-Engine: 2.5.0.283055, Antispam-Data: 2007.2.21.90434 X-Virus-Checked: Checked by ClamAV on apache.org > That implies that I'm that own the development cycle of this code.=20=20= =20 > In this case, I just get a jar from the user. With current facilities: 1. Unpack the entire content of the original jar to some "temp" directory. 2. Run enhancer with "temp" in classpath and *not* the original jar 3. Jar the "temp" directory=20 4. Overwrite the original jar, optinally This way, if the original content contained other files (meta-inf etc.) will be packaged exactly in the final jar. Enhancer will not require to handle rewriting of a Jar file's content.=20 =20 Pinaki Poddar BEA Systems 415.402.7317=20=20 _______________________________________________________________________ Notice: This email message, together with any attachments, may contain information of BEA Systems, Inc., its subsidiaries and affiliated entities, that may be confidential, proprietary, copyrighted and/or legally privileged, and is intended solely for the use of the individual or entity named in this message. If you are not the intended recipient, and have received this message in error, please immediately return this by email and then delete it.