Mailing-List: contact ivy-user-help@ant.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ivy-user@ant.apache.org
Received-SPF: pass (athena.apache.org: domain of ryan.fong@workday.com
 designates 72.32.253.78 as permitted sender)
User-Agent: Microsoft-Entourage/12.33.0.120411
Date: Wed, 01 Aug 2012 10:32:54 -0700
Subject: IvyDE 2.2.0.beta1 & Ant environment varaibles
From: Ryan Fong <ryan.fong@workday.com>
To: <ivy-user@ant.apache.org>
Message-ID: <CC3EB656.250%ryan.fong@workday.com>
Thread-Topic: IvyDE 2.2.0.beta1 & Ant environment varaibles
Thread-Index: Ac1wC66bqSz6pglwgEOAC6vzimkxDg==
Mime-version: 1.0
Content-type: multipart/alternative;
	boundary="B_3426661974_554014"

--B_3426661974_554014
Content-type: text/plain;
	charset="ISO-8859-1"
Content-transfer-encoding: quoted-printable

G=B9day, mates.  Our team has Ivy integrated with our Ant build files.  While
investigating Eclipse Juno w/ the IvyDE 2.2.0.beta1 plugin I discovered tha=
t
IvyDE has trouble resolving the environment variables that are dynamically
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 absolute
path which is different on each developer=B9s system.

I=B9d appreciate suggestions on how to get IvyDE working in this environment,
preferably without modifying the ivy.xml files.  Is this a limitation of th=
e
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.name}"/>
   =20
    <configurations>
        <include=20
file=3D"${my.build.dir}/common/default-ivy-configurations.xml"/>
-------

--B_3426661974_554014--