I assume that "Every time someone checks in new code, fire off a build" has a set minimum time. That it can spawn another build is based on the minimum required to do a build. This assumes also that whenever a person checks in code that it compiles. Also, do the constant builds produce the artifacts of the build (output a jar ,ear files, etc. each time)? Or is it expect just to compile the .java files into the .class files?
Paul Franz -----Original Message----- From: Paul Cody <[EMAIL PROTECTED]> Date: Tue, 26 Feb 2002 12:36:50 -0800 To: "'Ant Users List'" <[EMAIL PROTECTED]> Subject: RE: Compiling files 1 at a time > > > > Also, what exactly do you mean by "continuous integration"? > > > > Every time someone checks in new code, fire off a build. See > [http://cruisecontrol.sourceforge.net] > > > > > > never gets anything unless the build succeeds (a full > > compile from Perforce) > > > and all Junit tests succeed. But we have only about 750 > > sourcefiles, much > > > smaller than your situation. Asking your development tool > > (ant) to do a > > > transitive closure compilation function seems equivalent to > > an implicit need > > > for a more modular project structure. > > > > Also, what exactly do you mean by "transitive closure > > compilation function"? > > > > If you consider the set of java files as nodes and the class dependencies > between them as edges (thus forming a graph) and a starting point(s), > finding the maximum number of files that will compile based on traversal of > the class dependencies could be considered "transitive closure". Perhaps > I'm using the term loosely however. > > Paul > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > > -- _______________________________________________ Sign-up for your own FREE Personalized E-mail at Email.com http://www.email.com/?sr=signup -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
