It seems cobertura:clean should do that as well - that would be an enhancement request to make in it's issue tracker.
The way you can achieve it for now is to bind the clean plugin into the lifecycle to delete only that directory on every build. However, this will slow things down - it would seem to make more sense to clean when you need to clean (which is the case for all of the classes). - Brett 2008/10/6 Ole Laurisch <[EMAIL PROTECTED]>: > Hello, > > I'm using Cobertura for code coverage checks. Therefore I have the > following paragraph in my pom.xml: > > <plugin> > <groupId>org.codehaus.mojo</groupId> > <artifactId>cobertura-maven-plugin</artifactId> > <executions> > <execution> > <goals> > <goal>clean</goal> > <goal>check</goal> > </goals> > </execution> > </executions> > <configuration> > <check> > <branchRate>20</branchRate> > <lineRate>20</lineRate> > </check> > <maxmem>128m</maxmem> > </configuration> > </plugin> > > Now I have a class "Foo.class" that has no test coverage. Therefore the > coverage check, executed by running "mvn verify", fails. After deleting > the class "Foo" and rerunning "mvn verify" the coverage check stills fails > because the class "Foo.class" is still available in the folder > "target/generated-classes/cobertura/". > Is there a way to update this folder before every run without having to > clean the whole target folder by running "mvn clean"? > > Thanks in advance, > Ole > > -- > engram GmbH > Konsul-Smidt-Straße 8r > 28217 Bremen > Germany > Tel.: +49-[0]421-620298-0 > Fax: +49-[0]421-620298-999 > Handelsregister Bremen HRB 20782 > Geschäftsführer: Jens Wünderlich > Aufsichtsratsvorsitzender: Ralf Paslack > -- Brett Porter Blog: http://blogs.exist.com/bporter/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
