Return-Path: Delivered-To: apmail-maven-users-archive@www.apache.org Received: (qmail 60276 invoked from network); 26 Aug 2010 15:31:26 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 26 Aug 2010 15:31:26 -0000 Received: (qmail 53944 invoked by uid 500); 26 Aug 2010 15:31:24 -0000 Delivered-To: apmail-maven-users-archive@maven.apache.org Received: (qmail 53842 invoked by uid 500); 26 Aug 2010 15:31:23 -0000 Mailing-List: contact users-help@maven.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "Maven Users List" Reply-To: "Maven Users List" Delivered-To: mailing list users@maven.apache.org Received: (qmail 53834 invoked by uid 99); 26 Aug 2010 15:31:23 -0000 Received: from Unknown (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 26 Aug 2010 15:31:23 +0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of bimargulies@gmail.com designates 209.85.214.43 as permitted sender) Received: from [209.85.214.43] (HELO mail-bw0-f43.google.com) (209.85.214.43) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 26 Aug 2010 15:31:00 +0000 Received: by bwz16 with SMTP id 16so1540790bwz.30 for ; Thu, 26 Aug 2010 08:30:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:content-type; bh=XM48VHpzsusJxfmzYypPxN1WSPyHkIsrFYykgDmdM/k=; b=G69V2tWe9NDaqtEljMX5XO2rGdZxi/rna3UZ7rzyfDYlFlEXAP4Z74L1Ym73UZcihN G1jRd6qpQnDM2+olU7k+VYFCsACjWHbfMMN/entBh3FQ0P+EUr2yAuKt/uGATZFh7KWY jK1YuT5QhCCJDDpVrqG1fniKonx/DQW5A9F3I= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=Fhq0aei960WzO0afPwtNT+0ie6U3qbKJgDOy+ixP9py9EHBXGzjhZ1kVvW6VQf56M5 5d5XxMo2yxX/0yjx6ueGp8/oxNq1ENfvtTznNgfqEEuftgA+kENQb6hIeYtdQ8nKcrax SXHIl8gT4+6AaxcLcIgrX7Z1F/kBhi+FLrVFU= MIME-Version: 1.0 Received: by 10.204.179.19 with SMTP id bo19mr6236281bkb.209.1282836608510; Thu, 26 Aug 2010 08:30:08 -0700 (PDT) Received: by 10.204.78.202 with HTTP; Thu, 26 Aug 2010 08:30:08 -0700 (PDT) In-Reply-To: References: <357BF5D4-62B7-44CC-88F1-D6B7E8C03079@gmail.com> <08FE456826D5F548B15625A584177C16100CB053CA@Casenet2.cninc.com> <08FE456826D5F548B15625A584177C16100CB055E8@Casenet2.cninc.com> <08FE456826D5F548B15625A584177C16100CB05633@Casenet2.cninc.com> Date: Thu, 26 Aug 2010 11:30:08 -0400 Message-ID: Subject: Re: Correcting a groupID From: Benson Margulies To: Maven Users List Content-Type: text/plain; charset=UTF-8 X-Virus-Checked: Checked by ClamAV on apache.org On Thu, Aug 26, 2010 at 8:41 AM, Stephen Connolly wrote: > Why not have commons-net:commons-net become an empty jar which has a > dependency on org.apache.commons:net > > that way, anyone with the old GA coords will just have an empty jar on their > classpath and the correct jar as well i don't see it. Component A is sitting out there with a dependency on c-n:c-n:1 Component B has a dependency on A and also on c-n:c-n:1 Sebb changes the group ID. Now, A still depends on c-n:c-n:1 B depends on org.apache.commons.net:c-n:12, and on A And we've got two dueling versions in classpath. It doesn't help to release a new version c-n:c-n:12, since A isn't using a range, it's pointing at '1'. Am I missing something? > > On 26 August 2010 00:13, Benson Margulies wrote: > >> Let me recap the pain scenario here: >> >> Existing poms reference commons-net under the old group ID. >> >> commons-net releases a new version under a new group ID. >> >> Dependencies under the old group ID won't be seen as 'the same thing' >> as the new group ID, so >> >> a project that references the new group ID and has a dependency that >> uses the old group ID gets both in the classpath, and probably >> experiences chaos until repaired with exclusions. >> >> Unless maven grew a feature whereby the new artifact could explicitly >> declare itself a successor of the old one under the other name, this >> is unavoidable. Either don't rename or live with this as an annoyance >> to the users of the new version. Renaming packages might help, insofar >> as the two versions might then coexist happily. >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org >> For additional commands, e-mail: users-help@maven.apache.org >> >> > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@maven.apache.org For additional commands, e-mail: users-help@maven.apache.org