I'm evaluating Maven's suitability to manage multi-platform builds for a C++ product targeting WIN32 and *nix.
Not having applied Maven in the conventional Java context, I'm trying to map a hypothetical project onto the end goal of deploying a thing composed of multiple .exe files, .so or .dll libraries, resource files, etc. I'm aware of 'maven-native-plugin' (as well as 'cpp-tasks' from ant- contrib). That part seems obvious enough. I'm struggling with issue of granularity and how to use Maven, given the notion that each project should produce one primary output. Does that mean I would have a sub-project (module) for each .exe/.so and then use profile-based assembly/assemblies to deploy? Or does it mean I would need to define a specialized plug-in to compile/link apps and a new packaging type that represents the final deployment-ready arrangement. Cheers, Brad [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
