That one falls into the "really hard to do" category, at least for Ant. Cedric and I both looked at the source code, and there's no convenient way (without hacking the top level script and producing a hackystat-specific distribution of Ant) to get at the top-level targets.
That's a bug in the Ant API, if you ask me, but we haven't yet gotten ready to fight them about it.
It would be good to be able (as supplemental info) to provide all of the targets invoked during a build. We haven't quite got there yet, either, but it should be do-able.
Cheers, Philip
--On Thursday, March 24, 2005 12:21 PM -1000 Aaron Kagawa <[EMAIL PROTECTED]> wrote:
Cedric,
I noticed that the build sensor does not capture all Build Targets. For example, if I type "ant -q freshStart junitAll". Build information on "junitAll" will be sent to the server and nothing about the "freshStart" part. So, the only way to capture correct build data is to ensure that we only execute on target at a time. For example, "ant -q freshStart" and then "ant -q junitAll". Note that I never run "freshStart junitAll" separately, so I never have freshStart build data.
Does the buildTarget matter? Is that a feature or a bug? Or is that really hard to do?
thanks, aaron
