build-automation

I am trying to automate my build process with cmake. There is currently only one issue: Where is, in cmake's philosophy (if there is one), the best place to put the copying of data files. I have a library and a few examples. The examples need the data. I currently do the following: I use a custom command in each example's CMakeLists.txt to copy all the Data into the CMAKE_CURRENT_BINARY_DIR in a post-build step. I use this in my debugging workflow, so no install target is executed yet. This works quite well, but has certain drawbacks: The copying occurs everytime the project is built. With VS

I am using Maven2 to build a WAR project. Some properties files are dependent on the environment targeted for a release. I want to deliver, in addition of the WAR, a file called datasource.xml . This file already exists in my project directory, but contains properties that will be filtered during the build (i.e. some ${foo.bar} ). In others words, after running the command mvn clean install , I want to see in my target/ directory two files, my-webapp.war and datasource.xml . Note that datasource.xml must not be included in the my-webapp.war artifact! How can I do this? You can attach

We just published parts of our library ( Mango ) which is a Scala wrapper around Google Guava common libraries for Java. The library currently depends on Google Gauva 14.0, but we would like to add support for other versions as well. Is there a way in sbt , a build-automation tool for Scala and Java projects, to create maven like profiles, where each profile compiles against a different version of the respective Guava dependency, so we can include it in the continuous integration test matrix? Ideally, it should be possible to call sbt with something like: sbt test guava:14.0 sbt test guava:13

I am writing a batch file to automate a series of tasks. One of these tasks is to update the version of the dlls in my solution, by editing the assemblyinfo.cs file in the various projects in my solution; and then finally calling msbuild.exe to compile the solution. In this regard, is it possible to write a command line script to update the various assemblyinfo.cs files in my .net solution. I would prefer to call msbuild from the commandline itself and not create another msbuild scripted file. How does one do this using MSBuild? Is there any other way to do it? Thanks for your time... Editing