Return-Path: 
 <ivy-user-return-8611-apmail-ant-ivy-user-archive=ant.apache.org@ant.apache.org>
X-Original-To: apmail-ant-ivy-user-archive@www.apache.org
Delivered-To: apmail-ant-ivy-user-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 71791E66C
	for <apmail-ant-ivy-user-archive@www.apache.org>;
 Sun, 27 Jan 2013 08:28:32 +0000 (UTC)
Received: (qmail 1355 invoked by uid 500); 27 Jan 2013 08:28:31 -0000
Delivered-To: apmail-ant-ivy-user-archive@ant.apache.org
Received: (qmail 912 invoked by uid 500); 27 Jan 2013 08:28:23 -0000
Mailing-List: contact ivy-user-help@ant.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:ivy-user-help@ant.apache.org>
List-Unsubscribe: <mailto:ivy-user-unsubscribe@ant.apache.org>
List-Post: <mailto:ivy-user@ant.apache.org>
List-Id: <ivy-user.ant.apache.org>
Reply-To: ivy-user@ant.apache.org
Delivered-To: mailing list ivy-user@ant.apache.org
Delivered-To: moderator for ivy-user@ant.apache.org
Received: (qmail 92301 invoked by uid 99); 26 Jan 2013 22:26:31 -0000
X-ASF-Spam-Status: No, hits=1.5 required=5.0
	tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (nike.apache.org: domain of jmsignup@gmail.com designates
 209.85.220.169 as permitted sender)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:x-received:date:message-id:subject:from:to
         :content-type;
        bh=XuvfAD8zFvPM/vCq7Zd66xyqfi2uEJAWbcmI1bpOIhs=;
        b=NMZihqM/hMEJjEqH7HGZHqU0QE/63u+xauH3L88hZayMKP8BhoHpmnHuhkW6mBk/6L
         S6EZAdjlTqrdHCRwYFr6VUZKv98HpknL4xjhk7nSpLPh90v7YTwENHNINRWyGdxLYTmV
         oQNhFjSnRVeLMFqiG+yuUfGxm/YoSFyNNlhyGuYPPDfRTQ/XdVUDnTzCLl67EoSK2kIt
         KXsz//Ml0Ws8+dxhlt+iOikIPAglE3dt5mADLKikz/MiMK8DCNjTftVa8SJCPmP7GInH
         +ij/GtrpvwIn9/fFRjqjl0WRg6q6QZpC3qymly91YyHVYohuDPLen2TvhFiuYUzVpKP3
         LvkA==
MIME-Version: 1.0
X-Received: by 10.52.22.194 with SMTP id g2mr4712370vdf.91.1359239162261; Sat,
 26 Jan 2013 14:26:02 -0800 (PST)
Date: Sat, 26 Jan 2013 15:26:02 -0700
Message-ID: 
 <CA+b4vZ0yjLEFsXWbZMSv3a1i-tDOtNCzooVY2bcM+K74hKQuVg@mail.gmail.com>
Subject: buildlist and properties in ivy files
From: John McCarthy <jmsignup@gmail.com>
To: ivy-user@ant.apache.org
Content-Type: multipart/alternative; boundary=20cf307ac3f76e71aa04d43887c0
X-Virus-Checked: Checked by ClamAV on apache.org

--20cf307ac3f76e71aa04d43887c0
Content-Type: text/plain; charset=ISO-8859-1

Greetings.  I've recently become aware of the buildlist ant task and would
like to use it to simply my build process.  I starting prototyping but hit
a roadblock.  My ivy files have branch and revision information as
properties.  For example,
    <ivy-module ...>
  <info organisation="myOrg" module="moduleA" branch="${build.branch}"
revision="${build.version}">
     ...

When building and publishing, these properties are populated from a
properties file, build.properties.  Because of this, buildlist doesn't work
for me, giving me warnings of the following form,
    [ivy:buildlist] WARN: Non matching revision detected when sorting.
 myOrg#moduleB depends on myOrg#moduleA#branchA;revA, doesn't match
myOrg#moduleA#${build.branch};${build.version}

I've used the Jenkins ivy plugin, and it allows for specifying a ivy
properties file.  I think I need the same option for buildlist.  Does a
mechanism exist for loading a properties file for ivy files found in
buildlist?  If not, do you think buildlist could benefit from such an
enhancement?  I believe it would solve my issue, but would it help others
enough to submit an enhancement request?  I was thinking another property
such as ivyproperties which specifies a properties file relative to found
ivy files.  I can look into this if it's the right track.

This leads me to another question: is using properties like this bad
practice (what do others do)?  I don't think I can easily incorporate
dynamic revisions, if that's what's typical, but I can look into it.

Thanks for the time and feedback,

John

--20cf307ac3f76e71aa04d43887c0--