You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Jay Perry <bo...@gmail.com> on 2010/08/11 17:20:35 UTC
ordering of dependencies causes failures in mvn site
Hi,
We are having an issue when running mvn site and setting a dependencies in a
particular order.
Here is the order of dependencies that causes failures because a class isn't
found during the JavaDocs report generation.
<dependency>
<groupId>com.company.common</groupId>
<artifactId>bc-common</artifactId>
<version>1.0.0-SNAPSHOT</version>
</dependency>
<dependency>
<groupId>com.company.common</groupId>
<artifactId>bc-common</artifactId>
<version>1.0.0-SNAPSHOT</version>
<type>test-jar</type>
<scope>test</scope>
</dependency>
If we swap the ordering of the dependencies above the site generation
passes:
<dependency>
<groupId>com.company.common</groupId>
<artifactId>bc-common</artifactId>
<version>1.0.0-SNAPSHOT</version>
<type>test-jar</type>
<scope>test</scope>
</dependency>
<dependency>
<groupId>com.company.common</groupId>
<artifactId>bc-common</artifactId>
<version>1.0.0-SNAPSHOT</version>
</dependency>
After doing some debugging it looks like the bc-common test-jar is the only
thing included in the classpath when ordering the dependencies with test-jar
at the bottom. Looking to see if anyone has run into this.
Thanks,
Jay
Re: ordering of dependencies causes failures in mvn site
Posted by Anders Hammar <an...@hammar.net>.
Could it be this?
http://jira.codehaus.org/browse/MNG-4452
/Anders
On Wed, Aug 11, 2010 at 17:20, Jay Perry <bo...@gmail.com> wrote:
> Hi,
>
> We are having an issue when running mvn site and setting a dependencies in
> a
> particular order.
>
> Here is the order of dependencies that causes failures because a class
> isn't
> found during the JavaDocs report generation.
>
> <dependency>
> <groupId>com.company.common</groupId>
> <artifactId>bc-common</artifactId>
> <version>1.0.0-SNAPSHOT</version>
> </dependency>
> <dependency>
> <groupId>com.company.common</groupId>
> <artifactId>bc-common</artifactId>
> <version>1.0.0-SNAPSHOT</version>
> <type>test-jar</type>
> <scope>test</scope>
> </dependency>
>
> If we swap the ordering of the dependencies above the site generation
> passes:
>
> <dependency>
> <groupId>com.company.common</groupId>
> <artifactId>bc-common</artifactId>
> <version>1.0.0-SNAPSHOT</version>
> <type>test-jar</type>
> <scope>test</scope>
> </dependency>
> <dependency>
> <groupId>com.company.common</groupId>
> <artifactId>bc-common</artifactId>
> <version>1.0.0-SNAPSHOT</version>
> </dependency>
>
> After doing some debugging it looks like the bc-common test-jar is the only
> thing included in the classpath when ordering the dependencies with
> test-jar
> at the bottom. Looking to see if anyone has run into this.
>
> Thanks,
> Jay
>