There is also a command line version of ivy : http://ant.apache.org/ivy/history/latest-milestone/standalone.html
2008/8/28 Xavier Hanin <[EMAIL PROTECTED]>: > On Thu, Aug 28, 2008 at 6:35 PM, <[EMAIL PROTECTED]> wrote: > >> Not being terribly familar with Ivy, I am assuming there are times when the >> Ivy ant tasks set ant properties which are then referenced elsewhere in the >> build file. If a NAnt build calls ivy as an external process, how would >> such information be easily communicated? (Lots of less elegant options come >> to mind, but they all seem a bit awkward.) >> >> The above is based on the assumption that typical ivy ant task usage in a >> non-trivial build results in communication between tasks via properties. Is >> this assumption valid? >> Does such communication (if any) involve references or just value types? >> Value types are obviously much simplier to communicate between processes. > > Information is passed through references. But there isn't that much > information passed between tasks, and tasks themselves are only a thin layer > over Ivy core API. I don't know how it fits in a .Net build though. > > Xavier > > >> (I'm rapidly reaching the point where I need to take a much closer look at >> Ivy to avoid asking stupid questions.) >> >> Some responses suggest that requiring a jvm to be deployed as part of a >> .NET build is no big deal. I completely agree on this. >> >> On a side note, according to its website IKVM can be used to convert java >> libraries to .NET assemblies. Therefore a .NET version of Ivy (or any other >> library) created by IKVM will not require IKVM to be deployed, although >> surely there are some IKVM assemblies which will need to be available. >> (Just as with the jvm, I don't think it would be a huge deal if it needed to >> be.) >> >> --- On Thu, 8/28/08, Stefan Bodewig <[EMAIL PROTECTED]> wrote: >> >> From: Stefan Bodewig <[EMAIL PROTECTED]> >> Subject: Re: Nant version of Ivy >> To: dev@ant.apache.org >> Date: Thursday, August 28, 2008, 10:34 AM >> >> On Wed, 27 Aug 2008, <[EMAIL PROTECTED]> wrote: >> >> > Is there any ongoing effort to produce a .NET/NAnt version of Ivy? >> >> Are you looking for Ivy to support .NET assemblies or for a .NET >> implementation of Ivy's general functionality? >> >> If Ivy's features are enough to support .NET builds (strangely I'm >> more familiar with .NEt than with Ivy) you could certainly use Ivy >> from within NAnt or MSBuild. All it would take was a Java VM on the >> build machine (which doesn't sound worse than requiring IKVM) - I've >> once written NAnt and MSBuild tasks to run Ant - but must admit I've >> never used them: >> <http://stefan.samaflost.de/blog/en/dotNet/ant_for_nant_and_msbuild.html> >> >> Alternatively you could build the .NET projects from within Ant: >> <http://ant.apache.org/antlibs/dotnet/index.html> >> >> Stefan >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > > -- > Xavier Hanin - Independent Java Consultant > http://xhab.blogspot.com/ > http://ant.apache.org/ivy/ > http://www.xoocode.org/ > -- Gilles Scokart --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
