Hi Poonam,

sorry for not responding to your first post ... I must have missed that :-(
In general I initially setup my Artifactory to serve lib-release, 
plugin-release, lib-snapshot, plugin-snapshot, ... but noticed that this was 
hard to maintain, configure, got you into tons of trouble and didn't come with 
any benefit whatsoever.

The core part in my settings xml is this:

    <mirrors>
        <mirror>
            <mirrorOf>*</mirrorOf>
            <name>remote-repos</name>
            <url>https://my.artifactory.host/artifactory/libs-release</url>
            <id>remote-repos</id>
        </mirror>
    </mirrors>

So Maven sort of resolves everything from this url. On machines I don't need to 
deploy stuff to my repo this is also about all I have in the settings.xml. I 
guess the different plugin and snapshot repos make it easier to deploy stuff 
from your machine to that repository. At least I need them in Flexmojos in 
order to deploy stuff to the Sonatype nexus.

Chris



-----Ursprüngliche Nachricht-----
Von: Poonam Anand [mailto:[email protected]] 
Gesendet: Montag, 21. April 2014 11:59
An: [email protected]
Betreff: 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

Ok I  could find cause of this issue but not sure about correct way of doing 
this.

//Settings.xml

<repositories>
                <repository>
                          <snapshots>
                            <enabled>false</enabled>
                          </snapshots>
                          <id>central</id>
                          <name>libs-release</name>
                         
<url>http://station117.in.guavus.com:8081/artifactory/libs-release</url>
                        </repository>
                        <repository>
                          <snapshots />
                          <id>snapshots</id>
                          <name>libs-snapshot</name>
                         
<url>http://station117.in.guavus.com:8081/artifactory/libs-snapshot</url>
                        </repository>
            </repositories>
           <pluginRepositories>

                <pluginRepository>
                          <snapshots>
                            <enabled>false</enabled>
                          </snapshots>
                          <id>central</id>
                          <name>plugins-release</name>
                         
<url>http://station117.in.guavus.com:8081/artifactory/plugins-release</url>
                        </pluginRepository>
                        <pluginRepository>
                          <snapshots />
                          <id>snapshots</id>
                          <name>plugins-snapshot</name>
                         
<url>http://station117.in.guavus.com:8081/artifactory/plugins-snapshot</url>
                </pluginRepository>
            </pluginRepositories>

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:

    <groupId>com.adobe.flex</groupId>
    <artifactId>framework</artifactId>
    <version>4.10.0.20130801</version>

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.

Reply via email to