Return-Path: Delivered-To: apmail-cocoon-dev-archive@www.apache.org Received: (qmail 10178 invoked from network); 1 May 2007 06:55:10 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 1 May 2007 06:55:10 -0000 Received: (qmail 79723 invoked by uid 500); 1 May 2007 06:55:15 -0000 Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org Received: (qmail 79253 invoked by uid 500); 1 May 2007 06:55:14 -0000 Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: dev@cocoon.apache.org List-Id: Delivered-To: mailing list dev@cocoon.apache.org Received: (qmail 79242 invoked by uid 99); 1 May 2007 06:55:14 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 30 Apr 2007 23:55:14 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of ap-cocoon-dev@m.gmane.org designates 80.91.229.2 as permitted sender) Received: from [80.91.229.2] (HELO ciao.gmane.org) (80.91.229.2) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 30 Apr 2007 23:55:06 -0700 Received: from list by ciao.gmane.org with local (Exim 4.43) id 1HimFx-0002Kk-8Z for dev@cocoon.apache.org; Tue, 01 May 2007 08:54:37 +0200 Received: from d5153ca7c.access.telenet.be ([81.83.202.124]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 01 May 2007 08:54:37 +0200 Received: from jheymans by d5153ca7c.access.telenet.be with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 01 May 2007 08:54:37 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: dev@cocoon.apache.org From: Jorg Heymans Subject: Re: Exclusions does not work with dependency managment? Date: Tue, 01 May 2007 08:54:27 +0200 Lines: 52 Message-ID: References: <4635CC68.7020802@tuffmail.com> <463662EC.5090601@apache.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-2; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: d5153ca7c.access.telenet.be User-Agent: Thunderbird 2.0.0.0 (Macintosh/20070326) In-Reply-To: <463662EC.5090601@apache.org> Sender: news X-Virus-Checked: Checked by ClamAV on apache.org Grzegorz Kossakowski wrote: > I also tried dependency plug-in already and had the same results as you. > It does not mention dependency we are talking about. I have no idea why. > However, I'm almost sure. Try mvn eclipse:eclipse and import project. > You'll see avalon-framework-4.1.3.jar in build path added so it does > come from that module, doesn't it? Also, you'll see it while executing: > mvn install -X > > Can you verify my findings? Unfortunately yes :( [INFO] [eclipse:eclipse] [DEBUG] org.apache.cocoon:cocoon-sitemap-impl:jar:1.0.0-RC1-SNAPSHOT (selected for null) [DEBUG] commons-collections:commons-collections:jar:3.2:compile (selected for compile) [DEBUG] commons-jxpath:commons-jxpath:jar:1.2:compile (selected for compile) [DEBUG] junit:junit:jar:3.8:compile (applying version: 3.8.2) [DEBUG] junit:junit:jar:3.8.2:compile (applying scope: test) [DEBUG] junit:junit:jar:3.8.2:test (selected for test) [DEBUG] xml-apis:xml-apis:jar:2.0.2:compile (applying version: 1.3.02) [DEBUG] xml-apis:xml-apis:jar:1.3.02:compile (selected for compile) [DEBUG] commons-logging:commons-logging:jar:1.0:compile (applying version: 1.1) [DEBUG] commons-logging:commons-logging:jar:1.1:compile (selected for compile) [DEBUG] log4j:log4j:jar:1.2.12:compile (applying version: 1.2.14) [DEBUG] log4j:log4j:jar:1.2.14:compile (selected for compile) [DEBUG] logkit:logkit:jar:1.0.1:compile (selected for compile) [DEBUG] avalon-framework:avalon-framework:jar:4.1.3:compile (selected for compile) [DEBUG] javax.servlet:servlet-api:jar:2.3:compile (applying version: 2.4) [DEBUG] javax.servlet:servlet-api:jar:2.4:compile (selected for compile) [DEBUG] commons-collections:commons-collections:jar:2.0:compile (applying version: 3.2) [DEBUG] javax.servlet:servlet-api:jar:2.4:provided (not setting scope to: compile; local scope provided wins) It seems that the eclipse plugin is using some different (buggy) dependency resolution mechanism. Don't have time now to investigate further, will have another look later (perhaps its a confirmed bug in the plugin?) rgds Jorg