On Tue, 2003-06-17 at 20:56, Conor MacNeill wrote: > On Tue, 17 Jun 2003 03:56 pm, Ben Walding wrote: > > > > I blame Clover's absurd insistence on migrating everything to Ant > > tasks. But I'm just a grumpy mongrel. > > > > Clover's Ant tasks are provided as a convenience. The alternate property-based > operation from Clover 1.0 is still supported and even the new filesets are > made available through Ant references. So really, nothing has been migrated, > as such. > > Actually, we thought having Ant tasks would make the Clover plugin for Maven > easier to develop and maintain, although I'll admit I don't know much about > Maven plugins. > > Anyway, what would you prefer? What could Clover provide to make the Maven > Clover plugin development easier?
Something like the AspectJ compiler API would be nice. It's just a simple Java class that allows you to set the sourceroots as a standard classpath looking string (/home/jason/source;/home/bob/source or /home/jason/source:/home/bob/source) or the individual files. It basically leaves it up to you how you get those files. As a result it took me only a few minutes to make an AspectJ compiler plugin component (for maven-new). > Conor > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] -- jvz. Jason van Zyl [EMAIL PROTECTED] http://tambora.zenplex.org In short, man creates for himself a new religion of a rational and technical order to justify his work and to be justified in it. -- Jacques Ellul, The Technological Society --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
