Return-Path: Delivered-To: apmail-directory-users-archive@www.apache.org Received: (qmail 34860 invoked from network); 13 Jun 2009 04:00:24 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 13 Jun 2009 04:00:24 -0000 Received: (qmail 92593 invoked by uid 500); 13 Jun 2009 04:00:36 -0000 Delivered-To: apmail-directory-users-archive@directory.apache.org Received: (qmail 92509 invoked by uid 500); 13 Jun 2009 04:00:36 -0000 Mailing-List: contact users-help@directory.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@directory.apache.org Delivered-To: mailing list users@directory.apache.org Received: (qmail 92499 invoked by uid 99); 13 Jun 2009 04:00:35 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 13 Jun 2009 04:00:35 +0000 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: domain of elecharny@gmail.com designates 209.85.219.225 as permitted sender) Received: from [209.85.219.225] (HELO mail-ew0-f225.google.com) (209.85.219.225) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 13 Jun 2009 04:00:25 +0000 Received: by ewy25 with SMTP id 25so3516973ewy.25 for ; Fri, 12 Jun 2009 21:00:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:message-id:date:from :user-agent:mime-version:to:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=uYq2SJmIa68/4pJyY3J6B7/KZMqODb2p68+euM6Id5k=; b=NPdO8DH8h51avjw7hvBo8pFIjiy3S8HYFL/yV8mKDpH3U2vmntfD7U7Cho2/0uASrv 0RPsEi8RiotuOGI43wHqE+t2jg8wTTWW1wI1QbSfEmeoY2kOdnDQSFi/tUHxIRICfTRa a7SkgS/FXQvTBHFoTHFw5orb1TEfvL9j34u14= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; b=QIn5XX4gYkH+OLJHQP9BIGweWDnxROEytkNbVKWGp4J3h8W2Htvn+3zAgoq7v7uhgp GfnDbRKkGzcZt6UkZUDmIKSD4I3fRMC9QzUi/cv2dqzjY2vaKGTW/kWnVhUfRWRZcWIm kshqjo9sDO7MZGbc3FkvA2QUQRnNTovrfudEU= Received: by 10.210.129.19 with SMTP id b19mr1612975ebd.30.1244865604306; Fri, 12 Jun 2009 21:00:04 -0700 (PDT) Received: from ?192.168.0.1? (vol75-3-82-66-216-176.fbx.proxad.net [82.66.216.176]) by mx.google.com with ESMTPS id 5sm2086527eyf.38.2009.06.12.21.00.03 (version=TLSv1/SSLv3 cipher=RC4-MD5); Fri, 12 Jun 2009 21:00:03 -0700 (PDT) Sender: Emmanuel Lecharny Message-ID: <4A332445.2020504@nextury.com> Date: Sat, 13 Jun 2009 06:00:05 +0200 From: Emmanuel Lecharny User-Agent: Thunderbird 2.0.0.21 (X11/20090318) MIME-Version: 1.0 To: users@directory.apache.org Subject: Re: error resolving commons-io References: <5a5f94ac0906122006l760f3eccu93c37833fc9f3a2a@mail.gmail.com> In-Reply-To: <5a5f94ac0906122006l760f3eccu93c37833fc9f3a2a@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Virus-Checked: Checked by ClamAV on apache.org Craig Swing wrote: > When I try to resolve with this dependency: > > rev="1.5.4" /> > > I get the following error > > inconsistent module descriptor file found in ' > http://repo1.maven.org/maven2/org/apache/commons/commons-io/1.3.2/commons-io-1.3.2.pom': > bad organisation: expected='org.apache.commons' found='commons-io'; > > Looking at the org.apache.commons directory, the poms refer to the > organization as commons-io, thus the error. > > Is there something I can do to work around this? > The problem is that commons-io is defined in two places in the maven repository (probably a mistake). We have changed the dependency in trunk to point to commons-io instead of org.apache.commons-io. Now, I guess that you are trying to build your application including Apacheds, and you use commons-io somewhere else in your dependencies. > One solution to move the directory server files into a local repository and > modify the dependency to use commons-io as the organization. This seems > more of a hack to me and I'd prefer to avoid doing this. > atm, I'm not sure you have another workaround. It will probably be solved in 1.5.5 -- -- cordialement, regards, Emmanuel L�charny www.iktek.com directory.apache.org