Doxia dependencies declared as compile dep

GoogleCodeExporter commented 9 years ago

What steps will reproduce the problem?
1. The jscep POM declares the doxia-module-docbook-simple as a compile time 
dependency and this means that all project that include jscep will also pull in 
the doxia dependencies transitively. The current workaround requires excluding 
them in our POMs like so:

<dependency>
   <groupId>com.google.code.jscep</groupId>
   <artifactId>jscep</artifactId>
   <version>2.0.1</version>
   <exclusions>
        <exclusion>
            <artifactId>doxia-module-docbook-simple</artifactId>
            <groupId>org.apache.maven.doxia</groupId>
        </exclusion>
    </exclusions>
</dependency>

What is the expected output? What do you see instead?
These deps aren't needed to make use of the jscep API so it doesn't make sense 
for them to be compile time dependencies.

Please use labels and text to provide additional information.
According to this: 
http://maven.apache.org/doxia/doxia/doxia-modules/doxia-module-docbook-simple/ 
you should declare as a dependency only when you execute the site plugin which 
creates all the documentation for the project.

Original issue reported on code.google.com by hir...@gmail.com on 29 Apr 2013 at 4:20

GoogleCodeExporter commented 9 years ago

Original comment by da...@grant.org.uk on 3 May 2013 at 4:09

GoogleCodeExporter commented 9 years ago

Fixed in 
https://github.com/seize-the-dave/jscep/commit/cf4f80026fec6def3172409d5af28c2e7
35e1ecc

Original comment by david.gr...@adaptivelogic.co.uk on 21 May 2013 at 7:11

ugu5ma / jscep

Doxia dependencies declared as compile dep #92