Return-Path: 
 <ivy-user-return-8451-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 6C01BDB2C
	for <apmail-ant-ivy-user-archive@www.apache.org>;
 Wed,  1 Aug 2012 22:35:18 +0000 (UTC)
Received: (qmail 48390 invoked by uid 500); 1 Aug 2012 22:35:18 -0000
Delivered-To: apmail-ant-ivy-user-archive@ant.apache.org
Received: (qmail 48368 invoked by uid 500); 1 Aug 2012 22:35:18 -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
Received: (qmail 48359 invoked by uid 99); 1 Aug 2012 22:35:18 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Aug 2012 22:35:18 +0000
X-ASF-Spam-Status: No, hits=1.5 required=5.0
	tests=FSL_RCVD_USER,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (nike.apache.org: domain of tyados@gmail.com designates
 209.85.212.181 as permitted sender)
Received: from [209.85.212.181] (HELO mail-wi0-f181.google.com)
 (209.85.212.181)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Aug 2012 22:35:11 +0000
Received: by wibhm2 with SMTP id hm2so4309006wib.16
        for <ivy-user@ant.apache.org>; Wed, 01 Aug 2012 15:34:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:in-reply-to:references:from:date:message-id:subject:to
         :content-type;
        bh=hoV0e758Ew7PBPJUdEwpR0F9D5LsFYspN74uCI2L3j8=;
        b=0/+B8y0q8LWqx6LvLyUrSM3m97bSCyz++1HZrFwPWi3SrHQpcsfxoEaMS73x5+3HC4
         v7uVVz9bl9/ExQO6Hp4l7dld/S+xP1V3FiBEubQZ/iwiOby7ZwZxsNfmBK67buLAt2CW
         M/dG63+dtRaE/qcHIGjm1Y433u1jK/aNjI23uuAwE/9ii6QeeOXXUqlWOArVN4yScSG9
         xi5Bl6iAJ/G+M0AGe8uJ18ws6VAaZdlJrwcgFVQsSa34WUc3csavZ8WZm3AsVaVXBHqO
         vWVQntnR5u8Dlbok6qGqEpgwbwpLYmeRj6HyG46s2TB5YPbf7Nt0c69dV52P60Ad+7Xj
         y3LQ==
Received: by 10.180.81.38 with SMTP id w6mr19948942wix.10.1343860490999; Wed,
 01 Aug 2012 15:34:50 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.194.15.98 with HTTP; Wed, 1 Aug 2012 15:34:30 -0700 (PDT)
In-Reply-To: <CC3EB656.250%ryan.fong@workday.com>
References: <CC3EB656.250%ryan.fong@workday.com>
From: Eyad Ebrahim <tyados@gmail.com>
Date: Thu, 2 Aug 2012 00:34:30 +0200
Message-ID: 
 <CAJY86C-rR5JAxiyyo=5DZUtF_fYbFBBqQQjqbT+bJKFu7bTQMw@mail.gmail.com>
Subject: Re: IvyDE 2.2.0.beta1 & Ant environment varaibles
To: ivy-user@ant.apache.org
Content-Type: multipart/alternative; boundary=f46d044288c031963804c63be751

--f46d044288c031963804c63be751
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

In IvyDE you could import a property file.
So instead of wanting to use the properties of ant build.xml file, you
could create a some_property.properties:
1) ant build.xml uses <loadproperties file .... /> to include this file.
2) Use IvyDE settings section to include this same file [in the property
files section]

HOWEVER,
In case of your two properties (I will consider each one, since they are
inherently different):
1)  ant.project.name: I hard coded it, but you don't need to do that. The
approach I suggested up there would solve the problem. [of course I'm
considering it for your ivy.xml example you provided]
2) my.build.dir: I had the same thing and build.dir is a different
repository from all other repositories (but they point to the my.build.dir
as an environment variable):
   - If you don't mind setting this variable to each project, then put it
in the .properties file and use the previous approach.
   - if you want to use one variable for all projects, make sure to use
<property environment=3D"env" /> [not properties] in the ivysettings.xml
before you could use this variable inside your ivy.xml files.

I know I'm having some stupid details, but maybe you could adapt this to
your case.

All the best,
Eyad

P.S. I had to do a special trick for Jenkins to see the my.build.dir (which
is not an environment variable)

On Wed, Aug 1, 2012 at 7:32 PM, Ryan Fong <ryan.fong@workday.com> wrote:

> G=B9day, mates.  Our team has Ivy integrated with our Ant build files.  W=
hile
> investigating Eclipse Juno w/ the IvyDE 2.2.0.beta1 plugin I discovered
> that
> IvyDE has trouble resolving the environment variables that are dynamicall=
y
> provided by Ant.  For example, ${my.build.dir} and ${ant.project.name}
> vary
> for each of the projects we have.
>
> Although we can provide paths to hardcoded properties files to the plugin=
,
> it would require a customized file per project.  Additionally,
> ${my.build.dir} is used by a FileSystemResolver which requires an absolut=
e
> path which is different on each developer=B9s system.
>
> I=B9d appreciate suggestions on how to get IvyDE working in this environm=
ent,
> preferably without modifying the ivy.xml files.  Is this a limitation of
> the
> plugin?  Thanks!
>
> --------
> <?xml version=3D"1.0" encoding=3D"UTF-8"?>
> <ivy-module version=3D"2.0">
>     <info organisation=3D"${ivy.organisation}" module=3D"${ant.project.na=
me
> }"/>
>
>     <configurations>
>         <include
> file=3D"${my.build.dir}/common/default-ivy-configurations.xml"/>
> -------
>

--f46d044288c031963804c63be751--