build-process

I have the impression, that in the .NET-world, there is no real need for a Maven-like tool. I am aware that there is Byldan and NMaven (is it still alive?), but I have not yet seen a real-world project that uses them. Also in most .NET projects I have worked on, there never was voiced an need for a Maven-like tool. The problems Maven maven is addressing (automatic dependency-resolution, conventions based build structure ...) seem not to be so important in .NET. Is my perception correct? Why is this the case? What are people really using in .NET? No automatic dependency resolution at all? Are

What is the most minimal example of deploying a war to multiple tomcat servers using maven that can be written? I've tried the following URLs and asked the mailing list, but not coming up with anything that was short and would simply work. http://www.nabble.com/Deploying-to-Multiple-Servers-at-Once-td21592419.html The example should have the servers defined in the example somewhere (with sample usernames/passwords) Romain Linsolas The idea of Markus Lux can be also applied with a Maven2 solution, with the profiles management: <build> <plugins> <plugin> <groupId>org.codehaus.cargo</groupId>

I would like my Maven builds to run most unit tests. But there are unit tests in one project which are slower and I'd like to generally exclude them; and occasionally turn them on. Question : How do I do this? I know about -Dmaven.test.skip=true , but that turns off all unit tests. I also know about skipping integration tests, described here . But I do not have integration tests, just unit tests, and I don't have any explicit calls to the maven-surefire-plugin. (I am using Maven 2 with the Eclipse-Maven plugin). Romain Linsolas What about skipping tests only in this module ? In the pom.xml of

I am wondering what the popular or best way to organise your build assets and source code within a project is? Personaly I use /client/projectname/trunk/source/Solution Name.sln /client/projectname/trunk/source/Project.One /client/projectname/trunk/source/Project.Two /client/projectname/trunk/source/Project.Three /client/projectname/trunk/source/SQL/ /client/projectname/trunk/source/SQL/SomeScript.sql /client/projectname/trunk/libraries /client/projectname/trunk/resources/Nunit /client/projectname/trunk/resources/LLBLGEN /client/projectname/trunk/documentation /client/projectname/trunk/builds

I would like to know which dependency described in my pom.xml brings a transitive dependency in my target directory. To be more precise, I have the library "poi-2.5.1-final-20040804.jar" in my WEB-INF/lib directory and I would like to know which dependency in my pom.xml brings that. To add to @David Crow, here's a dependency:tree example from the Maven site: mvn dependency:tree -Dincludes=velocity:velocity might output [INFO] [dependency:tree] [INFO] org.apache.maven.plugins:maven-dependency-plugin:maven-plugin:2.0-alpha-5-SNAPSHOT [INFO] \- org.apache.maven.doxia:doxia-site-renderer:jar:1.0

I need to create some core libraries within my application which will be available in both .NET 3.5 and .NET 4.0. I'm happy creating multiple projects, creating the required defines and using #ifdef to control which code make it into which output assembly. However, what I would like to know is if there is a way of keeping those projects in sync? When I am developing under XNA, I have a Windows build and a Windows Phone build - and XNA injects a property into the project file called XnaCrossPlatformGroupID . What it does with that is enable Visual Studio to automagically make sure that when a