DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=40544>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=40544 ------- Additional Comments From [EMAIL PROTECTED] 2006-09-19 14:23 ------- I do know that Steve doesn't like Ant to be used for deployment (hence his SmartFrog project), but I hadn't seen anything about him disliking the idea of splitting tasks up for processing. I could for example see problems with compilation where various classes depend on one another and are compiled in different locations, etc. But certain tasks lend themselves to grid processing, such as those where a single operation is performed on multiple files one-by-one, and that operation is "state-less". That is there is no form of dependencies on either other files or operations. PMD is such a task. The reports generated from each grid resource can be combined with a simple xsl transformation. Of course if unit tests can be run across a grid (http://www.lsd.ufcg.edu.br/~alex/doku.php?id=gridunit), then I'm thinking it should be possible to also run coverage across a grid......(assuming you're not using a modified JVM to capture coverage data.). Most coverage tools offer the ability to merge coverage data, allowing you to merge the coverage data from the various grid resources. Whatever we may disagree on, I think we can certainly agree that the possibility of spreading your nightly builds across a grid is VERY enticing....there's a lot of free computing cycles on the desktops in the average corporate workplace. Also, another quick example of possible use for grid infrastructure is where you may have to repeat similar tasks during your build. Lets say you wanted to run findbugs and also Clover coverage on your code. Clover instruments your source right before it compiles, and Findbugs scans bytecode to check for errors. However, findbugs hates clover instrumented code, so you're forced to recompile the code (without Clover) just for Findbugs. Now imagine, you could have one machine handling the Findbugs run, while another runs the Clover Coverage report generator. That would be pretty damn neat. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
