flex-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Poonam Anand <Poonam.An...@guavus.com>
Subject Re: Flex mojos 6.0.1 and Flex SDK 4.10 - Failure to find com.adobe.flex:framework:pom: in artifactory even when it exist
Date Mon, 21 Apr 2014 09:58:56 GMT
Ok I  could find cause of this issue but not sure about correct way of doing


                          <snapshots />

                          <snapshots />

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:


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.

View raw message