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

Marcin Wisnicki updated IVY-1427:
---------------------------------

    Description: 
Attached example has 3 projects:

 * proj1 extends proj3 needs proj2
 * proj2 extends proj3
 * proj3

If you invoke ant in main directory you will see buildlist as:

 # proj2
 # proj1
 # proj3

Which is wrong since both proj1 and proj2 extend proj3 and therefore it should 
be first in order.

I have a multi-module project with staging directory and when module is being 
published before it's parent, ivy fails with exception "bad ivy file in cache".



  was:
Attached example has 3 projects:

 * proj1 extends proj3 needs proj2
 * proj2 extends proj3
 * proj3

If you invoke ant in main directory you will see buildlist as:

 # proj2
 # proj1
 # proj3

Which is wrong since both proj1 and proj2 extend proj3 and therefore it should 
be first in order.

I've a multi-module project with staging directory and when module is being 
published before it's parent, ivy fails with exception "bad ivy file in cache".



    
> buildlist has wrong order with module inheritance
> -------------------------------------------------
>
>                 Key: IVY-1427
>                 URL: https://issues.apache.org/jira/browse/IVY-1427
>             Project: Ivy
>          Issue Type: Bug
>          Components: Ant
>    Affects Versions: 2.2.0, 2.3.0
>            Reporter: Marcin Wisnicki
>         Attachments: ivy-buildlist.zip
>
>
> Attached example has 3 projects:
>  * proj1 extends proj3 needs proj2
>  * proj2 extends proj3
>  * proj3
> If you invoke ant in main directory you will see buildlist as:
>  # proj2
>  # proj1
>  # proj3
> Which is wrong since both proj1 and proj2 extend proj3 and therefore it 
> should be first in order.
> I have a multi-module project with staging directory and when module is being 
> published before it's parent, ivy fails with exception "bad ivy file in 
> cache".

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to