weiji wrote:
Thanks DD -- we are mostly an MS shop, but we do have a mixed set of
developers. I'm actually part of a dev group doing Java and we are already
using Ant for our build process (javac, junit, javadocs, deployment, even
some 3rd party tasks for compiling Adobe Flex code and remote ssh
connections to our staging server) and the success of this build process is
what is prompting our existing buildmasters to take a look. So far they are
very impressed, hence the desire to learn Ant rather than write a custom
build tool on their own.
The problem is that we (and by "we" I really mean myself) don't have much
prior experience with Ant, so "we" are learning it on the side (I picked up
Steve Loughran's book "Ant in Action" which has helped tremendously). I'd
like to be able to stick with Ant since we already have some part of the
company using it, and have one (very important) guy in the company as my
advocate.
Well, I guess I'd better help then.
The best way I've found to start VSS stuff is just to <exec with
failonerror="true"> MSBUILD.exe with the right command line options to
trigger the whole build of a composite solution. You leave your CI tool
churning for 30 minutes and then you either get a list of C++ link
errors, test failures or success.
The advantage of this approach is the VS folk can use the IDE to set
everything up, while you can use Ant, Cruise Control, Hudson or similar
to integrate the build with the rest of the project.
I haven't played with Ivy in this world...you could use Ivy to publish
the native/.NET artifacts and pull them in to other projects...
--
Steve Loughran http://www.1060.org/blogxter/publish/5
Author: Ant in Action http://antbook.org/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
