Return-Path: Delivered-To: apmail-db-torque-dev-archive@www.apache.org Received: (qmail 34523 invoked from network); 17 Oct 2007 08:25:18 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 17 Oct 2007 08:25:18 -0000 Received: (qmail 99156 invoked by uid 500); 17 Oct 2007 08:25:06 -0000 Delivered-To: apmail-db-torque-dev-archive@db.apache.org Received: (qmail 99143 invoked by uid 500); 17 Oct 2007 08:25:06 -0000 Mailing-List: contact torque-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "Apache Torque Developers List" Reply-To: "Apache Torque Developers List" Delivered-To: mailing list torque-dev@db.apache.org Received: (qmail 99132 invoked by uid 99); 17 Oct 2007 08:25:06 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 17 Oct 2007 01:25:06 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [217.24.207.26] (HELO mail.seitenbau.net) (217.24.207.26) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 17 Oct 2007 08:25:09 +0000 Received: from [192.168.15.18] (helo=www.seitenbau.net) by router.seitenbau.net with esmtp (Exim 4.43) id 1Ii4Cr-00046d-Is for torque-dev@db.apache.org; Wed, 17 Oct 2007 10:24:48 +0200 In-Reply-To: <47151E14.5080503@apache.org> Subject: Re: torque 3.3 schedule To: "Apache Torque Developers List" X-Mailer: Lotus Notes Release 7.0.1 January 17, 2006 Message-ID: From: Thomas Fischer Date: Wed, 17 Oct 2007 10:24:44 +0200 X-MIMETrack: Serialize by Router on www/seitenbau(Release 7.0.1|January 17, 2006) at 17.10.2007 10:24:44 AM MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII X-Spam-Score: -1.4 (-) X-Spam-Report: -1.4 ALL_TRUSTED Passed through trusted hosts only via SMTP X-Virus-Checked: Checked by ClamAV on apache.org a) we cannot use a m2 build only because the m1 plurgin needs an m1 build. And we cannot use a m1 build only because the m2 plugin needs a m2 build. So we have to use two types of repository at the moment and we cannot do anything against it. b) The m1:org.apache.torque is the long term goal. I'd not switch the group id in an rc. Also, having the two goup ids separates the two builds: group id "torque" are the m1 built files, group id "org.apache.torque" are the m2 built files. So I'd prefer to keept he the m1:torque, m2:org.apache.torque solution for 3.3. This does not mean I'm -1 on the other solution, it is just my personal preference. Thomas Thomas Vandahl schrieb am 16.10.2007 22:24:52: > Thomas Fischer wrote: > >> - I'd propose to put the resulting jar into the Maven repository in the > >> "torque" group or "org.apache.torque" respectively. What do others > >> say? > > > > m1:torque, m2:org.apache.torque is good. > > The repository people are bugging everybody to settle on one type of > repository only. Shouldn't we try to use one group only for Torque? I > propose to deploy the artifacts to the m2-repo only and use > 'org.apache.torque' for this. Would that create big obstacles for the > two maven plugins? > > Bye, Thomas. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: torque-dev-unsubscribe@db.apache.org > For additional commands, e-mail: torque-dev-help@db.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: torque-dev-unsubscribe@db.apache.org For additional commands, e-mail: torque-dev-help@db.apache.org