Return-Path: X-Original-To: apmail-flex-users-archive@www.apache.org Delivered-To: apmail-flex-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 2677511287 for ; Mon, 21 Apr 2014 10:00:07 +0000 (UTC) Received: (qmail 57486 invoked by uid 500); 21 Apr 2014 10:00:06 -0000 Delivered-To: apmail-flex-users-archive@flex.apache.org Received: (qmail 57243 invoked by uid 500); 21 Apr 2014 10:00:05 -0000 Mailing-List: contact users-help@flex.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@flex.apache.org Delivered-To: mailing list users@flex.apache.org Received: (qmail 57235 invoked by uid 99); 21 Apr 2014 10:00:03 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 21 Apr 2014 10:00:03 +0000 X-ASF-Spam-Status: No, hits=2.3 required=5.0 tests=SPF_SOFTFAIL,URI_HEX,WEIRD_PORT X-Spam-Check-By: apache.org Received-SPF: softfail (nike.apache.org: transitioning domain of Poonam.Anand@guavus.com does not designate 216.139.250.139 as permitted sender) Received: from [216.139.250.139] (HELO joe.nabble.com) (216.139.250.139) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 21 Apr 2014 09:59:59 +0000 Received: from [192.168.236.139] (helo=joe.nabble.com) by joe.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1WcB0J-0003T7-EF for users@flex.apache.org; Mon, 21 Apr 2014 02:59:11 -0700 Date: Mon, 21 Apr 2014 02:58:56 -0700 (PDT) From: Poonam Anand To: users@flex.apache.org Message-ID: <1398074336407-6210.post@n4.nabble.com> In-Reply-To: <1395895612734-5742.post@n4.nabble.com> References: <1395895612734-5742.post@n4.nabble.com> Subject: Re: Flex mojos 6.0.1 and Flex SDK 4.10 - Failure to find com.adobe.flex:framework:pom:4.10.0.20130801 in artifactory even when it exist MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Ok I could find cause of this issue but not sure about correct way of doing this. //Settings.xml false central libs-release http://station117.in.guavus.com:8081/artifactory/libs-release snapshots libs-snapshot http://station117.in.guavus.com:8081/artifactory/libs-snapshot false central plugins-release http://station117.in.guavus.com:8081/artifactory/plugins-release snapshots plugins-snapshot http://station117.in.guavus.com:8081/artifactory/plugins-snapshot We have repositories and pluginRepositories defined as above. libs-release has all flex sdk artifacts and plugins-release has compiler artifacts. If I change pluginRepositories url to repositories url, it builds in 1 go. Reason for that is with above settings.xml, when it tries to resolve compiler dependency defined in mojos plugin, it resolves all compiler dependencies successfully as all those present in pluginRepositories. Issue is with pom dependency defined in compiler which is as below: com.adobe.flex framework 4.10.0.20130801 Now this framework pom has further dependencies which are different flex sdk artifacts like advancedgrids, e.t.c. To resolve these, it tries to look in libs-release i.e repositories url which is correct and fails to find though they are present and could resolve in second fire. I cann't modify settings.xml or give different profiles as that is standard configuration across organization on different build machines and as per Maven 3 also, we should segregate repositories and pluginRepositories. Why does maven gets confused in this case? I can consider modifying pom to include repositories and pluginRepositories with same url - libs-release which has all sdk artifacts as well as compiler artifacts. But I tried doing this, it seems to ignore these configs which are defined in pom and still refers settings.xml ones. Another solution is to comment this framework dependency in compiler pom and deploy on our artifactory. I am not sure why this pom is included as compiler dependency, are any compiler libraries using this? In case of our project pom, I have this framework dependency included as project dependency. So will commenting this won't lead to any side-effects since this anyways looks redundant since we have this in project pom. -- View this message in context: http://apache-flex-users.2333346.n4.nabble.com/Flex-mojos-6-0-1-and-Flex-SDK-4-10-Failure-to-find-com-adobe-flex-framework-pom-4-10-0-20130801-in-at-tp5742p6210.html Sent from the Apache Flex Users mailing list archive at Nabble.com.