Thanks Volker, I've fixed it. Actually I don't know how it was working with the classpath element... Probably that in Maven 1.0.x the maven.dependency.classpath was added to the classloader in use when the <taskdef>/<typedef> were called...
In any case it's better to avoid some magic and to always specify it. Thanks -Vincent > -----Original Message----- > From: Volker Füßler [mailto:[EMAIL PROTECTED] > Sent: mardi 10 mai 2005 11:41 > To: users@maven.apache.org > Subject: [maven 1.1] Clover Tasks not found - a solution > > Hi, > > with maven 1.1 I had the problem, that the clover task definitions could > not be found. Her is my solution if you run into the same problems. > > I had to change the following 2 lines in the clover:init goal of > plugin.jelly of the maven-clover-plugin: > > <ant:taskdef resource="clovertasks" /> > <ant:typedef resource="clovertypes" /> > > to > > <ant:taskdef resource="clovertasks" classpathref="clover.classpath"/> > <ant:typedef resource="clovertypes" classpathref="clover.classpath"/> > > Regards, Volker > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
