Return-Path: Delivered-To: apmail-ant-notifications-archive@minotaur.apache.org Received: (qmail 75012 invoked from network); 15 Dec 2009 22:23:46 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 15 Dec 2009 22:23:46 -0000 Received: (qmail 21193 invoked by uid 500); 15 Dec 2009 22:23:46 -0000 Delivered-To: apmail-ant-notifications-archive@ant.apache.org Received: (qmail 21144 invoked by uid 500); 15 Dec 2009 22:23:46 -0000 Mailing-List: contact notifications-help@ant.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ant.apache.org Delivered-To: mailing list notifications@ant.apache.org Received: (qmail 21135 invoked by uid 99); 15 Dec 2009 22:23:46 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 15 Dec 2009 22:23:45 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 15 Dec 2009 22:23:44 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 17EF8234C4CA for ; Tue, 15 Dec 2009 14:23:23 -0800 (PST) Message-ID: <1387515373.1260915803097.JavaMail.jira@brutus> Date: Tue, 15 Dec 2009 22:23:23 +0000 (UTC) From: "Maarten Coene (JIRA)" To: notifications@ant.apache.org Subject: [jira] Commented: (IVY-1001) ivy:buildlist is not ordering modules properly when module name is defined as ${ant.project.name} In-Reply-To: <420939104.1231686119948.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/IVY-1001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12790991#action_12790991 ] 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... Maarten > 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. > 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 :-( > 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.