Return-Path: Delivered-To: apmail-repository-archive@www.apache.org Received: (qmail 58011 invoked from network); 30 May 2007 19:19:16 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 30 May 2007 19:19:16 -0000 Received: (qmail 7370 invoked by uid 500); 30 May 2007 19:19:20 -0000 Delivered-To: apmail-repository-archive@apache.org Received: (qmail 7298 invoked by uid 500); 30 May 2007 19:19:20 -0000 Mailing-List: contact repository-help@apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: repository@apache.org List-Id: Delivered-To: mailing list repository@apache.org Received: (qmail 7287 invoked by uid 99); 30 May 2007 19:19:20 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 30 May 2007 12:19:20 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of carlossg@gmail.com designates 66.249.92.173 as permitted sender) Received: from [66.249.92.173] (HELO ug-out-1314.google.com) (66.249.92.173) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 30 May 2007 12:19:09 -0700 Received: by ug-out-1314.google.com with SMTP id l31so270909ugc for ; Wed, 30 May 2007 12:18:48 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=qUPj9iFbJrS/BvqKyfWspGazk1Ll4YyFT+IMXRIZy875dDV5V2t9V4S+j0J8HBVJIojuAHhgksYqz28s/bcjCy92hDY0xsB6K9SVkXX0bLQvlqWuuYW082mrDSjvEgp2ajsFxQ5u+5K3UzSqmUI3WVg4YLpZJfvqqbHUuITjHOQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=PGpCk3hRtpYkmsWJRBNQVqYV/itaZhE1g2g9AGP4RT++Hf3fnZcByLxYGYzeoF9sDNuJuYrZTCc8Yw8pv1ek0FDU0YeTAFondBOdiM4TaLOVre8TlQW3Xdv4pKShzy7TyqtkJEl1orYxroIka1OX27qn+Y5WDJNidFaBf8w/H/M= Received: by 10.67.27.15 with SMTP id e15mr758649ugj.1180552727740; Wed, 30 May 2007 12:18:47 -0700 (PDT) Received: by 10.66.241.12 with HTTP; Wed, 30 May 2007 12:18:47 -0700 (PDT) Message-ID: <1a5b6c410705301218m3f0e24cbnc4df23e93893022a@mail.gmail.com> Date: Wed, 30 May 2007 12:18:47 -0700 From: "Carlos Sanchez" Sender: carlossg@gmail.com To: "Nick Burch" Subject: Re: Wrong pom for poi 3.0-FINAL Cc: repository@apache.org In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <1a5b6c410705211039s333351bdre71eefa019e96863@mail.gmail.com> X-Google-Sender-Auth: d4852d0bccfce275 X-Virus-Checked: Checked by ClamAV on apache.org On 5/22/07, Nick Burch wrote: > On Mon, 21 May 2007, Carlos Sanchez wrote: > > The pom for poi 3.0-FINAL is not correct. > > I'm not a maven user, so I asked on the users list, and followed the > directions of the maven users there. They all thought the form we released > was going to be fine :/ > > > I see that you use the new groupId org.apache.poi, if you use it then > > we need to put pom and jar in > > http://people.apache.org/repo/m1-ibiblio-rsync-repository/org.apache.poi > > instead of http://people.apache.org/repo/m1-ibiblio-rsync-repository/poi > > For now, I've added a symlink. doesn't work like that, the metadata has groupId information and you can't point two folders to the same metadata I have copied the jars to org.apache.poi and fixed the poms The one in poi redirects to org.apache.poi The one in org.apache.poi has the dependency, license and all the other info, please check it into subversion for next releases http://people.apache.org/repo/m1-ibiblio-rsync-repository/org.apache.poi/poms/ > > Going forward, we think we ought to be using org.apache.poi rather than > poi. What's the recommended way to deal with moving to a qualified > groupId, wrt old releases? Should we have a symlink, or should we keep the > old ones under /poi/, and new ones under /org.apache.poi/? you can't do just a symlink for the metadata. As it stands right now people using "poi" location for 3.0-FINAL will get a warning that it has moved to "org.apache.poi" so they update their dependencies accordingly > > Thanks > Nick > -- I could give you my word as a Spaniard. No good. I've known too many Spaniards. -- The Princess Bride