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 lists@nabble.com designates
 216.139.236.158 as permitted sender)
Message-ID: <26010005.post@talk.nabble.com>
Date: Thu, 22 Oct 2009 06:34:17 -0700 (PDT)
From: Jaikiran <jai_forums2005@yahoo.co.in>
To: ivy-user@ant.apache.org
Subject: Re: AW: Programmatic use of Ivy
In-Reply-To: <52018A29A797D040B8F643A7A9F60F1403BF3573@hamburg.blau.de.local>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
References: <25973730.post@talk.nabble.com>
 <52018A29A797D040B8F643A7A9F60F1403BF3573@hamburg.blau.de.local>


Klaas,

You are right about the tight coupling with Ant properties. I spent some
time looking into the Ivy code and it definitely makes it difficult to use
it outside of the Ant tasks. Although, i could get the minimal
resolve/retrieve features working with some of the Ivy APIs (keeping Ant out
of the equation), there are some other APIs like the reporting ones which i
found almost impossible to use without those Ant properties.

As of now, i have documented the minimal set of APIs i got to work in the
wiki http://cwiki.apache.org/confluence/display/IVY/Programmatic+use+of+Ivy.
If anyone wants to add/edit there, feel free to do so. I might have to look
into some more APIs like the conflict resolution ones in the near future. I
hope those are usable!
-- 
View this message in context: http://www.nabble.com/Programmatic-use-of-Ivy-tp25973730p26010005.html
Sent from the ivy-user mailing list archive at Nabble.com.