Mailing-List: contact ivy-user-help@ant.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ivy-user@ant.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
Message-ID: <20080117170954.vd88c2s9kowc4kso@intranet.digizenstudio.com>
Date: Thu, 17 Jan 2008 17:09:54 -0500
From: Jing Xue <jingxue@digizenstudio.com>
To: ivy-user@ant.apache.org
Subject: RE: IVYDE - what are the alternatives?
References: 
 <93B3B6122B906D44BC7E8B8CEFB0DBBB1843F56020@SGP-EXCHANGE.pointserve.com>
In-Reply-To: 
 <93B3B6122B906D44BC7E8B8CEFB0DBBB1843F56020@SGP-EXCHANGE.pointserve.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset=UTF-8;
	DelSp="Yes";
	format="flowed"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
User-Agent: Internet Messaging Program (IMP) H3 (4.1.4)


Quoting "Loehr, Ruel" <rloehr@pointserve.com>:

> +1.
>
> I like the idea of having an xsl to do this (I'm a little   
> embarrassed that I didn't think of it before).   I'd be happy to   
> help you work on it or test it.
>
> I had written an ant task to do the same sort of thing, but XSL   
> would be a lot simpler.

I wrote my own ant task to do that, too, which uses ant xml task to  
manipulate .classpath.

My turn-off with IvyDE is it runs ivy.xml+ivysettings.xml without  
going through the same ant script used to make official builds. We  
have lots of property and environment settings done in ant before  
invoking ivy, so the "naked" ivy files just won't work.

Cheers.
-- 
Jing Xue