On Wed, Aug 27, 2008 at 9:55 PM, <[EMAIL PROTECTED]> wrote: > Is there any ongoing effort to produce a .NET/NAnt version of Ivy? (I > suppose this would be "NIvy".)
I don't think so. > > > I find myself wondering if this can be easily done by using IKVM to convert > the > Ivy bytecode to IL along with NAnt based clones of the Ivy Ant tasks. > > Any guidance on the most practical/expedient approach? Any rough > estimation of effort? I'm guessing this is only a week or two of work if > IKVM works smoothly, but I don't really know. I'm familiar enough with the .NET platform to give an opinion. But what would be the advantage of such a version? Is having a jvm on the build machine really the issue? Xavier > > Is there any interest by Ant committers to adopt such a product if I took > the time to author it? If so, any guidance on how to ensure it would be > adopted? I assume some amount of simple automated integration/smoke tests > would need to be created. > > Thanks for your time and effort spent responding to this post. > > References: > IKM site: http://www.ikvm.net/ > > P.S.: I am considering either a Nant/msbuild/Ivy or an NMaven based build > solution for a rather large componetized C# build. Unfortunately, both > solutions looks like they will involve a great deal of bloodletting. Is > there another/better choice for obtaining proper dependency and build > artifact management of C# code? Without such features I'm not sure how to > maintain manageablity of a large build process. -- Xavier Hanin - Independent Java Consultant http://xhab.blogspot.com/ http://ant.apache.org/ivy/ http://www.xoocode.org/
