[ 
https://issues.apache.org/jira/browse/IVY-1617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Algassimou Diallo updated IVY-1617:
-----------------------------------
    Description: 
Hi all,
 I have the following repository
  
{noformat}
+---------------+  conf1<-conf3   +---------------+
| org#module3;2 | <-------------- | org#module1;1 | -+
+---------------+                 +---------------+  |
  |                                 |                |
  |                                 | conf3->conf1   | conf2->conf2
  |                                 v                |
  |                               +---------------+  |
  |                +------------- | org#module2;1 | <+
  |                |              +---------------+
  |                |                |
  |                | conf1->conf1   | conf2->conf2
  |                |                v
  |                |              +---------------+
  |                +------------> | org#module3;1 |
  |                               +---------------+
  |                                 |
  |                                 | conf2->conf2
  |                                 v
  |               conf2->conf2    +---------------+
  +-----------------------------> | org#module4;1 |
                                  +---------------+
{noformat}
I do a resolve on org#module1 in three different cases and for each case I 
think I should not found the org#module4 in the dependencies of the conf3 
configuration report:

1- with only the conf3, I don't find it 
 2- with conf3 and conf2 in this order, I don't find it 
 3- with conf2 and conf3 in this order, the org#module4 is present.

The resolve process is dependent on the order I specify the confs to resolve.
 Is that the correct behavior?

You'll find attached the repository and a Junit test which expose this behavior.

Best Regards

 

  was:
Hi all,
 I have the following repository
  
{noformat}
+---------------+  conf1<-conf3   +---------------+
| org#module3;2 | <-------------- | org#module1;1 | -+
+---------------+                 +---------------+  |
  |                                 |                |
  |                                 | conf3->conf1   | conf2->conf2
  |                                 v                |
  |                               +---------------+  |
  |                +------------- | org#module2;1 | <+
  |                |              +---------------+
  |                |                |
  |                | conf1->conf1   | conf2->conf2
  |                |                v
  |                |              +---------------+
  |                +------------> | org#module3;1 |
  |                               +---------------+
  |                                 |
  |                                 | conf2->conf2
  |                                 v
  |               conf2->conf2    +---------------+
  +-----------------------------> | org#module4;1 |
                                  +---------------+
{noformat}
I do a resolve on org#module1 in three different cases and for each case I 
think I should not found the org#module4 in the dependencies of the conf3 
configuration report:

1- with only the conf3 it is this case 
2- with conf3 and conf2 in this order it is the case
3- with conf2 and conf3 in this order it is not the case

The resolve process is dependent on the order I specify the confs to resolve.
Is that the correct behavior?

You'll find attached the repository and a Junit test which expose this behavior.

Best Regards

 


> Resolve and confs order
> -----------------------
>
>                 Key: IVY-1617
>                 URL: https://issues.apache.org/jira/browse/IVY-1617
>             Project: Ivy
>          Issue Type: Bug
>    Affects Versions: 2.5.0
>            Reporter: Algassimou Diallo
>            Priority: Major
>         Attachments: IVY-Confs.zip, TestConfs.java
>
>
> Hi all,
>  I have the following repository
>   
> {noformat}
> +---------------+  conf1<-conf3   +---------------+
> | org#module3;2 | <-------------- | org#module1;1 | -+
> +---------------+                 +---------------+  |
>   |                                 |                |
>   |                                 | conf3->conf1   | conf2->conf2
>   |                                 v                |
>   |                               +---------------+  |
>   |                +------------- | org#module2;1 | <+
>   |                |              +---------------+
>   |                |                |
>   |                | conf1->conf1   | conf2->conf2
>   |                |                v
>   |                |              +---------------+
>   |                +------------> | org#module3;1 |
>   |                               +---------------+
>   |                                 |
>   |                                 | conf2->conf2
>   |                                 v
>   |               conf2->conf2    +---------------+
>   +-----------------------------> | org#module4;1 |
>                                   +---------------+
> {noformat}
> I do a resolve on org#module1 in three different cases and for each case I 
> think I should not found the org#module4 in the dependencies of the conf3 
> configuration report:
> 1- with only the conf3, I don't find it 
>  2- with conf3 and conf2 in this order, I don't find it 
>  3- with conf2 and conf3 in this order, the org#module4 is present.
> The resolve process is dependent on the order I specify the confs to resolve.
>  Is that the correct behavior?
> You'll find attached the repository and a Junit test which expose this 
> behavior.
> Best Regards
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to