I want to drop some thoughts into the discussion. We are a shop using both Java and .Net. I am using Maven for all my projects and having a build process which is based on Maven. Beside the well know benefits of Maven, a big point for using it, is the versioning and reproducibility. We have products and components which you could easily put together in different versions. Maven (and the Archiva Repository Server we use) helps us at this point.
Now I have seen NMaven and I tried to port the ideas of the Java World to the .net one. At this point I have seen the (mentioned) problems Maven has (for the .Net world). I also would like to help to NMaven community, because I like the project very much, but it is very confusing where to start. (There is a release (0.14) which seems to be used, but for me it doesn't work. And there is the trunk, which I think needs much work to be done, e.g. it seems important to have a VS Plugin to generate solutions out of poms and vice versa.) And thats the point. I don't know how a migration could solve this issue. I also think, that you could use the help of the maven developer, if there are problems, but I don't know how this was in the history. I don't know how much maven related things could be reused by NMaven, but I think reusing code is better as developing new things in an other language. I think we should go out to the .net community and show them what the benefits of NMaven are instead of simply capitulating. I haven't seen something simular to maven in the .net world. In the next days I will talk to some german alt.net guys and see what there opinion is.
