ant-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Maarten Coene (JIRA)" <>
Subject [jira] Commented: (IVY-1001) ivy:buildlist is not ordering modules properly when module name is defined as ${}
Date Tue, 15 Dec 2009 22:23:23 GMT


Maarten Coene commented on IVY-1001:

Carlton: I'm not sure it's a bug because if you don't specify the status in your ivy.xml file,
it will default to "integration" and "latest.milestone" doesn't match the status "integration".

Pavel: I don't know what Ivy can do to solve this problem. Maybe indeed only some extra documentation
for the ivy:buildlist task that you should be carefull when the ivy.xml file contains properties...


> ivy:buildlist is not ordering modules properly when module name is defined as ${}
> -------------------------------------------------------------------------------------------------
>                 Key: IVY-1001
>                 URL:
>             Project: Ivy
>          Issue Type: Bug
>    Affects Versions: 2.0-RC2
>         Environment: windows vista
>            Reporter: Pavel Savara
>         Attachments:
> 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 ${}, which is related to build.xml in module.
>     <info 
>         organisation="net.sf.robocode"
>         module="${}"
>         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="${}"
> with
>         module="robocode.core"
> Everything is fixed and you get correct order.
> I spend 4 hours until I found what's wrong :-( 
> As well because it was my first serious attempt to use Ivy so I was no learning curve
same time.
> I think we need fix it if it is bug, or document that ant properties are not OK in Ivy
files and warn user if possible.

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

View raw message