Return-Path: Delivered-To: apmail-jakarta-commons-dev-archive@www.apache.org Received: (qmail 84086 invoked from network); 22 Jan 2004 06:08:13 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 22 Jan 2004 06:08:13 -0000 Received: (qmail 21647 invoked by uid 500); 22 Jan 2004 06:07:45 -0000 Delivered-To: apmail-jakarta-commons-dev-archive@jakarta.apache.org Received: (qmail 21585 invoked by uid 500); 22 Jan 2004 06:07:45 -0000 Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Jakarta Commons Developers List" Reply-To: "Jakarta Commons Developers List" Delivered-To: mailing list commons-dev@jakarta.apache.org Received: (qmail 21572 invoked from network); 22 Jan 2004 06:07:45 -0000 Received: from unknown (HELO sccrmhc12.comcast.net) (204.127.202.56) by daedalus.apache.org with SMTP; 22 Jan 2004 06:07:45 -0000 Received: from 192.168.123.60 (c-24-14-39-135.client.comcast.net[24.14.39.135]) by comcast.net (sccrmhc12) with SMTP id <20040122060755012004q6cne> (Authid: stevecoh1); Thu, 22 Jan 2004 06:07:56 +0000 From: Steve Cohen To: "Jakarta Commons Developers List" Subject: Re: [net] release question Date: Thu, 22 Jan 2004 00:07:55 -0600 User-Agent: KMail/1.5 References: <200401211429.04289.scohen@javactivity.org> <85fze982r5.fsf@brekke.org> In-Reply-To: <85fze982r5.fsf@brekke.org> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200401220007.55241.scohen@javactivity.org> X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N I see. After looking further into this matter, I begin to doubt the correctness of the http://jakarta.apache.org/commons/releases/prepare.html instructions. They recommend this line in the manifest Implementation-Title: "org.apache.commons.foo" The existing maven system produces Package: "org.apache.commons.net" To me, "Package" is a more descriptive key than "Implementation-Title" for this value anyway. I will stick with what Maven does. On Wednesday 21 January 2004 2:29 pm, Jeffrey D. Brekke wrote: > I used what maven put in there. > > >>>>> On Wed, 21 Jan 2004 14:29:04 -0600, Steve Cohen > >>>>> said: > > > > I am now working on preparing release 1.1.1 of jakarta-commons/net > > and I have come to the point of working on the jar manifest as > > detailed in: > > > > http://jakarta.apache.org/commons/releases/prepare.html > > > > What we now have in the jar manifest does not fit this pattern, and > > I am wondering where the current pattern comes from. Is it default > > stuff that maven and/or produces? We don't have a > > jakarta-commons/net/src/conf/MANIFEST.MF. Should we? > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org > > For additional commands, e-mail: commons-dev-help@jakarta.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org For additional commands, e-mail: commons-dev-help@jakarta.apache.org