Hi, We are using Maven for building a multi-language project with both Java, C# and C++. For the C# projects we have been using NMaven since this spring. Currently we use a version of NMaven from late spring but we trying to upgrade to head as we speak.
I haven't been coding that much C# myself (more Java and Maven) though so I apologize if some of my comments are off target. Given our aim our main priority is: 1) NMaven should be as tightly integrated with Maven as possible. As we have a multi-language build all things that require special treatment are a problem. For example: - The repository layout should be identical to Maven (I am not enough into C# to understand the problem with having versions in dll names) - Maximum reuse of existing Maven plugins. For example, I have tried using the dependency plugin for extracting artifacts from the repository (both Java and C#) but it fails for C# artifacts because the type coordinate "library" is assumed to be file extension which means it won't find C# dlls. - No local installation (except the compiler of course). NMaven should be downloaded from remote repository as other plugins. Currently we can't delete our local repos as we have to rerun bootstrap-build again then. - Snapshot support We only target Windows for C# so Mono support is not a priority for us. However, support for Visual Studio 2008 will become a priority very soon. We tried running bootstrap-build with Studio 2008 but it failed. Regarding generation of csproj or pom.xml we would prefer generating csproj from pom.xml in the same way as the eclipse plugin generates eclipse projects. In a multi-language environment common configuration (in pom.xml) is very valuable. To sum it up: A stable build that works as similar to Maven for Java as possible, possibly at the expense of C# specific features, is our target. Peter -- View this message in context: http://www.nabble.com/Need-Some-Feedback-tf4333020.html#a12392657 Sent from the nmaven-dev mailing list archive at Nabble.com.
