I created a small example of the problem and put it here:
http://pastebin.com/QDhx2kVf
Just run that pom.xml (I have tried Maven 2.2.1 and Maven 3.0.3) with this
command:
mvn install cobertura:cobertura
If it is truly skipping the cobertura plugin, you should only see this line
once:
[echo] Running antrun plugin....
But you actually see it twice.
I also tried this with -X as requested and the value appears to be set to true
below.
[DEBUG] -----------------------------------------------------------------------
[DEBUG] Goal:
org.codehaus.mojo:cobertura-maven-plugin:2.5.1:instrument (default-cli)
[DEBUG] Style: Regular
[DEBUG] Configuration: <?xml version="1.0" encoding="UTF-8"?>
<configuration>
<attach default-value="false">${cobertura.attach}</attach>
<classifier default-value="cobertura">${cobertura.classifier}</classifier>
<dataFile
default-value="${project.build.directory}/cobertura/cobertura.ser">${cobertura.datafile}</dataFile>
<forceMojoExecution
default-value="false">${cobertura.force}</forceMojoExecution>
<instrumentation>${instrumentation}</instrumentation>
<maxmem default-value="64m">${cobertura.maxmem}</maxmem>
<mojoExecution default-value="${mojoExecution}"/>
<pluginClasspathList default-value="${plugin.artifacts}"/>
<project default-value="${project}"/>
<quiet default-value="false">${quiet}</quiet>
<skip default-value="false">true</skip>
</configuration>
I'm not putting this into the reporting bit (yet).
-Jim
-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of Robert
Scholte
Sent: Monday, December 12, 2011 1:57 PM
To: [email protected]
Subject: RE: skip cobertura for a module
If you run 'mvn cobertura:cobertura -X' (-X means debug-level logging) you
should see the used configuration.
Can you confirm there's a skip-parameter and that its value is true?
The pluginManagement doesn't work for reporting-plugins, so within the
reporting-section you are required to specify the version.
-Robert
> From: [email protected]
> To: [email protected]
> Subject: RE: skip cobertura for a module
> Date: Mon, 12 Dec 2011 19:41:04 +0000
>
> Robert,
>
> Thanks much for the response. I have a parent pom that does just that in its
> pluginManagement section. Under the heading of "it never hurts to try", I
> went ahead and tried putting this in the offending module:
>
> <plugin>
> <groupId>org.codehaus.mojo</groupId>
> <artifactId>cobertura-maven-plugin</artifactId>
> <version>2.5.1</version>
> <configuration>
> <skip>true</skip>
> </configuration>
> </plugin>
>
> It's still having the same problem.
>
> Thanks!
>
> -Jim
>
> -----Original Message-----
> From: [email protected] [mailto:[email protected]] On Behalf Of
> Robert Scholte
> Sent: Monday, December 12, 2011 1:33 PM
> To: [email protected]
> Subject: RE: skip cobertura for a module
>
>
> Try to set the version of the plugin to 2.5.1
>
> It is a good practice to always set the version for every plugin.
>
> Maven-3.0.x already warns you about it and it will probably be required one
> day.
>
>
>
> -Robert
>
>
>
> ps. why not just run 'mvn install site'? This should already trigger these
> plugins if you have defined them in the reporting-section.
>
> > From: [email protected]
> > To: [email protected]
> > Subject: skip cobertura for a module
> > Date: Mon, 12 Dec 2011 19:19:40 +0000
> >
> > Hello all,
> >
> > I tried posting this on the codehaus user list but it won't accept my
> > e-mails. So let's try here:
> >
> > I'm having an issue with the cobertura plugin. I have a muti-module build
> > that I invoke like this on a nightly basis:
> >
> > mvn install site:site findbugs:findbugs cobertura:cobertura
> >
> > Now all of the modules in the build should build using cobertura, except
> > one. We have some custom stuff that is not entirely the "Maven way" and
> > want to ignore it for the sake of running cobertura (it does not contain
> > code anyway). Here's where I start hitting trouble. It seems that I cannot
> > get the skip to work. It always at least runs the prepare. It's not
> > corbertura that's failing (one of our in house plugins unfortunately), but
> > I don't want that prepare to run at all.
> >
> > Ideally I would just use a skip like this:
> >
> > <plugin>
> > <groupId>org.codehaus.mojo</groupId>
> > <artifactId>cobertura-maven-plugin</artifactId>
> > <configuration>
> > <skip>true</skip>
> > </configuration>
> > </plugin>
> >
> > But when I put that in, it still invokes cobertura. At least I see it say
> > this:
> >
> > [INFO] Preparing cobertura:cobertura
> >
> > And it proceeds to run all the other plugins again. To be pedantic, I tried
> > this as well:
> >
> > <plugin>
> > <groupId>org.codehaus.mojo</groupId>
> > <artifactId>cobertura-maven-plugin</artifactId>
> > <configuration>
> > <skip>true</skip>
> > </configuration>
> > <executions>
> > <execution>
> > <goals>
> > <goal>clean</goal>
> > <goal>check</goal>
> > <goal>cobertura</goal>
> > <goal>dump-datafile</goal>
> > <goal>instrument</goal>
> > </goals>
> > </execution>
> > </executions>
> > </plugin>
> >
> > But that had similar results.
> >
> > I also tried putting this property in the pom:
> >
> > <properties>
> > <cobertura.skip>true</cobertura.skip>
> > </properties>
> >
> > Again, that did not stop it from running the prepare bit. It seems to
> > always run the prepare.
> >
> > How do I turn cobertura off for this one module?
> >
> > -Jim
> >
> >
> > ---------------------------------------------------------------------
> > 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]
>
>
>
>
> ---------------------------------------------------------------------
> 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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
