Use the <apply> task. It executes a command once for each file. Specify the files by means of filesets or any other resource. <apply> is built-in; no additional dependency needed; no custom task implementation needed. It’s also possible to run the command only once, appending all files as arguments in one go. Use the parallel … Read more
In order to use source map, you should change devtool option value from true to the value which available in this list, for instance source-map devtool: ‘source-map’ devtool: ‘source-map’ – A SourceMap is emitted.
Makefile part of the question This is pretty easy, unless you don’t need to generalize try something like the code below (but replace space indentation with tabs near g++) SRC_DIR := …/src OBJ_DIR := …/obj SRC_FILES := $(wildcard $(SRC_DIR)/*.cpp) OBJ_FILES := $(patsubst $(SRC_DIR)/%.cpp,$(OBJ_DIR)/%.o,$(SRC_FILES)) LDFLAGS := … CPPFLAGS := … CXXFLAGS := … main.exe: $(OBJ_FILES) g++ … Read more
Pre- and Post-Build Events run as a batch script. You can do a conditional statement on $(ConfigurationName). For instance if $(ConfigurationName) == Debug xcopy something somewhere
Very similar question and good answers here: #include all .cpp files into a single compilation unit? The summary seems to be that less I/O overhead is the major benefit. See also The Magic Of Unity Builds as linked in the above question as well.
1) Use maven dependency plugin Create a simple project with pom.xml only. Add your dependency and run: mvn dependency:tree (Version for multi-module Maven project: mvn compile dependency:tree ) Unfortunately dependency mojo must use pom.xml or you get following error: Cannot execute mojo: tree. It requires a project with an existing pom.xml, but the build is … Read more
There are legitimate uses of –whole-archive when linking executable with static libraries. One example is building C++ code, where global instances “register” themselves in their constructors (warning: untested code): handlers.h typedef void (*handler)(const char *data); void register_handler(const char *protocol, handler h); handler get_handler(const char *protocol); handlers.cc (part of libhandlers.a) typedef map<const char*, handler> HandlerMap; HandlerMap … Read more
Actually, I didn’t check what the maven-shade-plugin is doing exactly (or any other plugin) as maven 2 has everything built-in to create a megajar or uberjar. You just have to use the maven-assembly-plugin with the predefined jar-with-dependencies descriptor. Just add this snippet to your pom.xml to customize the manifest: <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-assembly-plugin</artifactId> <configuration> <archive> <manifest> … Read more
Actually, I think that the answer given in the question you mentioned is just wrong (UPDATE – 20101106: someone fixed it, this answer refers to the version preceding the edit) and this explains, at least partially, why you run into troubles. It generates two jar files in logmanager/target: logmanager-0.1.0.jar, and logmanager-0.1.0-jar-with-dependencies.jar. The first one is … Read more
In my opinion, to answer this question, you need to think in terms of project life cycle and version control. In other words, does the parent pom have its own life cycle i.e. can it be released separately of the other modules or not? If the answer is yes (and this is the case of … Read more