Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Jakarta Commons Developers List" <commons-dev@jakarta.apache.org>
Received-SPF: pass (herse.apache.org: domain of phil.steitz@gmail.com
 designates 66.249.92.175 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=peWF6O1sdlW/lFAMBlE+qzth3AaFwtUpRENGfeID6Lv9QbxtRO5zVJ9KqE3QdhNvJKUzXLVLRaGVtg3Hi+ra5Cx30WSl4QXIEgxuoOFn7xnFCd0tPpgQHzyU+S7QcLQ/YbEDOIY5CfbxTfIUgGpBEdtQrvqalIkcRwpujBf2Tvk=
Message-ID: <8a81b4af0706032149je07403cxbaff8cf9ad987435@mail.gmail.com>
Date: Sun, 3 Jun 2007 21:49:36 -0700
From: "Phil Steitz" <phil.steitz@gmail.com>
To: "Jakarta Commons Developers List" <commons-dev@jakarta.apache.org>
Subject: Re: [vote] releasing jci RC3 as 1.0 ...maybe this time?
In-Reply-To: <A7B1239F-D9C9-4247-8D69-B68E69128225@apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <A7B1239F-D9C9-4247-8D69-B68E69128225@apache.org>

Sigs and hashes check fine, but I had to grab your key from
http://www.apache.org/dist/jakarta/bcel/KEYS.  Make sure to add this
under JCI somewhere (see below)

* I think that for consistency and at least to provide a definitive
location for the release artifacts, KEYS, and release notes, we should
continue the practice of rolling combined zips/tarballs and putting
these on the mirrors under /dist/jakarta-commons.  The separate jars
in [cli] are pretty small, so the "who needs what" issue is not really
a big one here, IMO.

** It is not clear to me how to build the binaries from the provided
sources.  The *sources* jars contain java source code. Do I need to
unpack this code with a common root and use the pom in
/org/apache/commons/commons-jci/1.0/commons-jci-1.0.pom?  I think we
should provide either a conventional source distribution or some
instructions on how to unpack and build the sources

* by itself is not a showstopper for me, but ** is.  I think a basic
requirement that we have is that release binaries can be built from
the sources in our distributions.  In the m1 days, we used to say
"maven clean dist" or at least "ant clean dist" needs to work from the
unpacked source distribution.  I don't care if it is a shell script,
ant, maven, or provided instructions, but users should have an obvious
and effective way to build from the sources in our releases.  Sorry if
I am just missing the obvious way to do this using m2.

Phil

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org