From open-jpa-dev-return-343-apmail-incubator-open-jpa-dev-archive=incubator.apache.org@incubator.apache.org Tue Aug 15 19:49:34 2006 Return-Path: Delivered-To: apmail-incubator-open-jpa-dev-archive@locus.apache.org Received: (qmail 98640 invoked from network); 15 Aug 2006 19:49:34 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 15 Aug 2006 19:49:34 -0000 Received: (qmail 83213 invoked by uid 500); 15 Aug 2006 19:49:34 -0000 Delivered-To: apmail-incubator-open-jpa-dev-archive@incubator.apache.org Received: (qmail 83147 invoked by uid 500); 15 Aug 2006 19:49:34 -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 83138 invoked by uid 99); 15 Aug 2006 19:49:34 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 15 Aug 2006 12:49:34 -0700 X-ASF-Spam-Status: No, hits=1.9 required=10.0 tests=DNS_FROM_RFC_ABUSE,DNS_FROM_RFC_POST,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of plinskey@bea.com designates 63.96.176.25 as permitted sender) Received: from [63.96.176.25] (HELO uslcmh01.bea.com) (63.96.176.25) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 15 Aug 2006 12:49:33 -0700 Received: from ussjfe01.amer.bea.com (ussjfe01b.bea.com [172.16.120.57]) by uslcmh01.bea.com (Switch-3.2.2/Switch-3.2.2) with ESMTP id k7FJn3Ke020704 for ; Tue, 15 Aug 2006 15:49:10 -0400 Received: from repbex02.amer.bea.com ([10.160.26.99]) by ussjfe01.amer.bea.com with Microsoft SMTPSVC(5.0.2195.6713); Tue, 15 Aug 2006 12:48:08 -0700 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: Update version to SNAPSHOT Date: Tue, 15 Aug 2006 12:48:05 -0700 Message-ID: <7D856CDFE035FF45A0420ACBD71BDD6301B9217E@repbex02.amer.bea.com> In-Reply-To: <3AE6AF4B-3247-4D42-AB73-8FD8B0B8FA2E@visi.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Update version to SNAPSHOT Thread-Index: AcbAo5m7l8g4AubXTPCCFOJlj61hHwAABeJg From: "Patrick Linskey" To: X-OriginalArrivalTime: 15 Aug 2006 19:48:08.0256 (UTC) FILETIME=[BB615C00:01C6C0A3] X-PMX-Version: 4.7.0.111621, Antispam-Engine: 2.0.2.0, Antispam-Data: 2006.8.15.101443 X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N > > So would it be easier to write a merge-manifest method or to=20=20 > > restrict manifest services with the same name to one of the build=20=20 > > modules? >=20 > Sorry, I think I'm making things clear as mud :) I get the feeling=20= =20 > we don't even have the issue Brett was mentioning. Aside from the=20=20 > MANIFEST.MF file itself, are there any jars of our own that contain=20=20 > the same file in the same place in the jar and those contents are=20=20 > different and need to be merged together? Yes. -Patrick _______________________________________________________________________ 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.