Yes, though native support for (8) isn't particularly strong or easy. Different Maven plugins tend to help with that support in specific domains.
You might be interested in looking at NPanday (http://incubator.apache.org/npanday/), which already provides some integration with VS, .sln files and msbuild - though it is focused at .NET C# and VB and may need some changes to support C++. You might also be interested in the "NAR" plugin, though I'm not sure what it's latest home is. - Brett On 01/10/2010, at 7:07 AM, Phillip Hellewell wrote: > Hi all, > > I'm investigating Maven for use at my company and would like to know if it > will support our desired workflow. Mainly I need to know if there are any > major issues that could not be solved with plugins. > > 1. Manage C++ and C# projects. > 2. Manage artifacts at the .sln level, not the .vcproj level. > 3. Append SVN tag name automatically to the artifact version. > 4. Compile phase simply invokes MSBuild.exe on the .sln using the > exec-maven-plugin. > 5. Create separate packages for headers, static libs, and dlls produced by a > build. > 6. For dependencies, specify which packages are needed (e.g., only dlls). > 7. Ability to obtain not only a packaged dependency from a remote to a local > repository, but also the ability to check out the source code for that > dependency from SVN, build it, and install it to the local repository. > 8. Use profiles to indicate the type of build a developer cares about (e.g., > Release|x64), and have this profile apply to every stage (fetching > dependencies, compile, install). > > Thanks, > Phillip -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
