Is it possible for Clover for Ant to generate instrumented source and class files into a separate directory from the uninstrumented files ? While searching the documentation I found references for enabling this with the IDE plugins, but not for the Ant targets.
I need to know whether this is possible in order to determine whether we can include Clover in our continuous integration builds, or whether we should create separate code coverage builds to generate the Clover data.
Sure - our Ant build system was set up to use EMMA for code coverage, which as you know only instruments byte code; it was pretty easy to separate out the instrumented classes for running tests while using non-instrumented classes for the distribution. With Clover, we had trouble filtering out instrumented classes from our distribution because it instruments the source as well, and so some of our compiled classes ended up with instrumentation in them. I'm sure we could have resolved this, but we felt it wasn't worth the effort since we get nearly all the features we need with Cobertura, for free. We've also been able to extend Cobertura for some custom requirements, since it's open source.
Over the next several weeks we'll be sharing some of our Getting Started guides here in the community. Throughout this series of posts, we'd love to hear from customers and non-customers ab...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs