NMaven is a set of extensions built on top of Maven. That means you have to install the Java JDK to use it. As people complain now because you have to install NAnt to build Castle, I figured it wasn't an option. The fact that Maven pulls down a ridiculous number of JARs to run means that it would probably be very difficult to compile Maven core with ikvmc -- assuming it would even work. Ivy is a lot easier because it has a much smaller code base.
On Feb 17, 11:56 am, Ayende Rahien <[email protected]> wrote: > Also checkout:- horn > - NMaven > > On Tue, Feb 17, 2009 at 11:00 AM, Eric Hauser <[email protected]> wrote: > > > This is something I have been thinking about for awhile and thought I > > would throw it out there. Since the project is going to be split > > apart into multiple components and most of the components have > > dependencies on each other, is it time to have something to manage the > > dependencies? Currently, I think this represents a large barrier in > > adopting open source .NET software for some -- what version of Windsor/ > > NHibernate are you using, where do you go to get them, etc. > > > This doesn't necessarily mean writing something. I was able to > > compile Ivy (http://ant.apache.org/ivy/) using IKVM a couple months > > ago, and run the command line version under .NET just fine. You can > > get quick integration with NAnt by provided a wrapper task that just > > execs the command line. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Castle Project Development List" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/castle-project-devel?hl=en -~----------~----~----~----~------~----~------~--~---
