build-process

Can anyone explain what advantages there are to using a tool like MSBuild (or NAnt) to build a collection of projects versus running DevEnv.exe from the command-line? A colleague I had worked with in the past had explained that (at least with older versions of Visual Studio) using DevEnv.exe was much slower than the other techniques, but I haven't read any evidence of that or if that is now a moot point now that starting with 2005, Visual Studio uses MSBuild under the hood. I know one advantage of using MSBuild allows you to build your projects without requiring Visual Studio to be installed

I have a set of projects which all need to run the same series of Maven plugin executions during their builds. I'd like to avoid re-declaring all of this configuration in every project, so I made them all inherit from a parent pom "template" project which only contains those plugin executions (8 different mojos). But I want those plugin executions to only run on the child projects and not on the parent project during Maven builds. I've tried to accomplish this four different ways, each with a side-effect I don't like. Declare the plugin executions in the parent pom's build/plugins element and

I'm looking for a good and easy in maintenance portable build system for C++ projects. Main platforms should include Windows (Visual Studio 8+) and Linux (gcc); Cygwin may be an advantage. We're considering two main possibilities: CMake and Boost.Jam . SCons can be also an option, but I haven't investigated it yet. CMake and Boost.Jam seem to have the following traits: CMake: (+) generates native "makefile" (solution for Windows, project for Eclipse) (+) extensions for testing and packaging (-) demands a configuration file in every project folder (-) based on a little too verbose peculiar

I'm developing a Java application using Eclipse. My project has two source directories that are both built and then some files are copied into the output folder. From the output directory I then run my application and all works well. However, I keep having these warnings: Snapshot from Problems tab in Eclipse http://www.freeimagehosting.net/uploads/128c1af93f.png Anyone know how to get rid of these warnings? Maybe by excluding some files, maybe based on the .svn extension or filename, from the build process? If so, how would I go about excluding those? Have you tried to add **/.svn/ to the

You know, the one that outputs this=> ------ Clean started: Project: Foo.Bar, Configuration: Debug Any CPU ------ ========== Clean: 1 succeeded, 0 failed, 0 skipped ========== What it is cleaning? The output directories - it removes the code that it's previously built. It doesn't remove the bin/obj directories themselves (or the Debug/Release directories beneath them), just the actual .exe, .dll, etc files. Unfortunately this makes it less useful for my usual use of cleaning up output directories: when I want to zip up the source code. As the Clean action doesn't do this, I usually just delete