I want to use Cobertura for code coverage, but its dependencies are
interfering with my XML parsing and Jetty serving. I'm able to resolve most
of these by using <exclusion>'s, but Maven is somehow *still* putting one
dependency in particular, jetty servlet-api, on the CLASSPATH.

pom.xml:

...
  <dependencies>
    <dependency>
      <groupId>net.sourceforge.cobertura</groupId>
      <artifactId>cobertura</artifactId>
      <version>2.0.3</version>
      <exclusions>
        <exclusion>
          <groupId>org.mortbay.jetty</groupId>
          <artifactId>servlet-api</artifactId>
        </exclusion>
      </exclusions>
    </dependency>
  </dependencies>
...

As confirmed by `mvn dependency:tree`, cobertura is still bringing jetty's
servlet-api onto the CLASSPATH. Am I doing something wrong?

-- 
Cheers,

Andrew Pennebaker
apenneba...@42six.com

Reply via email to