Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 6276 invoked from network); 2 Dec 2005 01:13:43 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 2 Dec 2005 01:13:43 -0000 Received: (qmail 17544 invoked by uid 500); 2 Dec 2005 01:13:42 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 17505 invoked by uid 500); 2 Dec 2005 01:13:41 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 17496 invoked by uid 99); 2 Dec 2005 01:13:41 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Dec 2005 17:13:41 -0800 X-ASF-Spam-Status: No, hits=1.4 required=10.0 tests=HTML_MESSAGE,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (asf.osuosl.org: 68.142.198.202 is neither permitted nor denied by domain of mcintyre.a@gmail.com) Received: from [68.142.198.202] (HELO smtp103.sbc.mail.mud.yahoo.com) (68.142.198.202) by apache.org (qpsmtpd/0.29) with SMTP; Thu, 01 Dec 2005 17:15:07 -0800 Received: (qmail 98389 invoked from network); 2 Dec 2005 01:13:16 -0000 Received: from unknown (HELO ?192.168.0.5?) (fuzzylogic@sbcglobal.net@67.127.58.155 with plain) by smtp103.sbc.mail.mud.yahoo.com with SMTP; 2 Dec 2005 01:13:16 -0000 Mime-Version: 1.0 (Apple Message framework v746.2) In-Reply-To: References: Content-Type: multipart/alternative; boundary=Apple-Mail-1-559972053 Message-Id: <4A0C779B-A5E1-4E5D-9E11-E668F8B83037@gmail.com> From: Andrew McIntyre Subject: Re: Please put Derby 10.1.2.1 in the Maven repository Date: Thu, 1 Dec 2005 17:13:14 -0800 To: X-Mailer: Apple Mail (2.746.2) X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N --Apple-Mail-1-559972053 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed On Dec 1, 2005, at 4:49 PM, sissonj@insession.com wrote: > > The Geronimo project would like to upgrade to Derby 10.1.2.1 but we > need the Derby JARs placed in the Maven repository. > > From memory Jeremy Boynes checked in some Maven files into the > maven directory that allow you to do this. Note that the > project.xml file will probably need to be edited to set the correct > version for the release. > > Placing the JARs in the Maven repository probably needs to be > documented as part of the project's release procedures, as this > didn't happen at release time for the previous (10.1.1.0) release. Hi John, Thanks for mentioning it. Could you please add a detailed procedure to the DerbySnapshotOrRelease wiki page: http://wiki.apache.org/db-derby/DerbySnapshotOrRelease See step 18 for "Deploy to Maven repository." I just copied what Jeremy sent in his last mail on the subject around the 10.1.1.0 release time. Could you please update this and add any details necessary to actually complete the deployment, taking into account that the person doing the deploying may have never used maven before? Kathey Marsden got to this step in the release instructions and wasn't sure what to do. Clearly these instructions are not sufficient, since the key part, the maven multiproject:deploy target, had been disabled as mentioned by Jeremy. Since I didn't do it last time either, I was unable to help her. It seems like someone who is already experienced with maven could flesh this out a lot faster than one of us groping around for the right settings in the right places. Thanks! andrew --Apple-Mail-1-559972053 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=ISO-8859-1

On Dec 1, = 2005, at 4:49 PM, sissonj@insession.com = wrote:


The Geronimo = project would like to upgrade to Derby 10.1.2.1 but we need the Derby = JARs placed in the Maven repository.

=46rom memory Jeremy Boynes checked in some Maven = files into the maven directory that allow you to do this. =A0Note that = the project.xml file will probably need to be edited to set the correct = version for the release.

Placing the JARs in the Maven repository probably = needs to be documented as part of the project's release procedures, as = this didn't happen at release time for the previous (10.1.1.0) = release.=A0

Hi John,

Thanks for mentioning it. = Could you please add a detailed procedure to the DerbySnapshotOrRelease = wiki page:


See step 18 for "Deploy to = Maven repository." I just copied what Jeremy sent in his last mail on = the subject around the 10.1.1.0 release time. Could you please update = this and add any details necessary to actually complete the deployment, = taking into account that the person doing the deploying may have never = used maven before?

Kathey Marsden got to this = step in the release instructions and wasn't sure what to do.=A0Clearly = these instructions are not sufficient, since the key part, the maven = multiproject:deploy target, had been disabled as mentioned by Jeremy. = Since I didn't do it last time either, I was unable to help her. It = seems like someone who is already experienced with maven could flesh = this out a lot faster than one of us groping around for the right = settings in the right places.

Thanks!

andrew
= --Apple-Mail-1-559972053--