Return-Path: X-Original-To: apmail-maven-users-archive@www.apache.org Delivered-To: apmail-maven-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id D0CDDE139 for ; Wed, 5 Dec 2012 01:26:41 +0000 (UTC) Received: (qmail 2117 invoked by uid 500); 5 Dec 2012 01:26:39 -0000 Delivered-To: apmail-maven-users-archive@maven.apache.org Received: (qmail 1968 invoked by uid 500); 5 Dec 2012 01:26:39 -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 36814 invoked by uid 99); 4 Dec 2012 20:00:47 -0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of batrdmi@gmail.com designates 209.85.210.171 as permitted sender) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=KoX3cT0zk66xrewKErYc6LqkNKNqTgZ3I901yfHmQ84=; b=rtctZtsOODxrw4cbGjXYPh+MgEtIFyWuQjsvhzkBl01apJ3rykGDEPAexAY0U2dq/8 RN8iZP+0VsbUBF77BIgNNKNjD6tvZiRYxgrAzAT1B03p50CiHeLOOO8W17YHE4PCtGiu CwGVrs8IpXVafedpLI8QI0575o+ZmSyicW1Mk2nPdstXACN/xkZpZ443g1cAeKz+d1nU 5DeaKkjbULI/3a2KAX6VPpbswnVPkav6blSLBMHHk8k1Cz7DPu/8J3pjHF+PaOYKKp+k 5Ug363iG2RtQ1gb2KOIc2b5fSiTfbgQn+c2gxCmKfvy1ZAGIKfAq43G4j59jUB/IkgCG fd4A== MIME-Version: 1.0 Date: Wed, 5 Dec 2012 00:00:19 +0400 Message-ID: Subject: Wrong resolution of dependency scope by Maven 3? From: Dmitry Batrak To: users@maven.apache.org Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Checked: Checked by ClamAV on apache.org Hi, While trying to migrate a project from Maven 2 to Maven 3, I encountered a problem, the essence of which can be demonstrated by the following simple example. Consider the following POM: 4.0.0 test A 1.0 org.apache.axis2 axis2-xmlbeans 1.5 provided org.apache.axis2 axis2-codegen 1.5 org.apache.geronimo.specs geronimo-stax-api_1.0_spec Running 'mvn dependency:resolve' for this POM yields a strange result. Namely, it says that that my module depends on geronimo-stax-api_1.0_spec with 'compile' scope. This artifact is a transitive dependency of both axis2-xmlbeans and axis2-codegen, and, according to rules for transitive dependencies, I would expect the resolved scope of geronimo-stax-api_1.0_spec to be 'provided'. With Maven 2 I get exactly the result I expect. Should I raise a JIRA ticket for this issue, or am I missing some point, and this is the desired behaviour in the new version of Maven? For reference - I used Maven version 3.0.4. I also checked the above with the latest version (2.6) of dependency plugin - result was the same. Best regards, Dmitry Batrak --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@maven.apache.org For additional commands, e-mail: users-help@maven.apache.org