[jira] Updated: (IVY-1001) ivy:buildlist is not ordering modules properly when module name is defined as ${ant.project.name}

["Pavel Savara (JIRA)" <ji...@apache.org>]

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

Pavel Savara updated IVY-1001:
------------------------------

    Attachment: projects.zip

> ivy:buildlist is not ordering modules properly when module name is defined as ${ant.project.name}
> -------------------------------------------------------------------------------------------------
>
>                 Key: IVY-1001
>                 URL: https://issues.apache.org/jira/browse/IVY-1001
>             Project: Ivy
>          Issue Type: Bug
>    Affects Versions: 2.0-RC2
>         Environment: windows vista
>            Reporter: Pavel Savara
>         Attachments: projects.zip
>
>
> I have multimodule solution.
> I wanted to save myself from repeating module name on two places so I replaced name of module in ivy.xml with ${ant.project.name}, which is related to build.xml in module.
>     <info 
>         organisation="net.sf.robocode"
>         module="${ant.project.name}"
>         status="integration"/>
> After such change, ivy:buildlist is giving wrong order of modules and no warning. 
> I will attach zip with example of such behavior.
> I have following dependencies:
> robocode.api<-robocode.core<-robocode.battle
> When you run any toplevel task which includes ivy:buildlist i.e. clean, you will get following (alphabetical?) order
> robocode.api
> robocode.battle
> robocode.core
> Which is wrong, because  battle depends on core.
> If you visit robocode.core\ivy.xml and replace
>         module="${ant.project.name}"
> with
>         module="robocode.core"
> Everything is fixed and you get correct order.
> I spend 4 hours until I found what's wrong :-(

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.