maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rob Vesse (JIRA)" <>
Subject [jira] (MSHADE-148) Shade Plugin gets stuck in infinite loop building dependency reduced POM
Date Thu, 06 Jun 2013 16:36:03 GMT


Rob Vesse commented on MSHADE-148:

As a naive suggestion for a fix from a non-maven expert why does the step of creating a dependency-reduced-pom
not just throw out test scoped dependencies completely?

test scoped dependencies are not transitive anyway so there is no real reason to include them
in the DPR for an uber jar
> Shade Plugin gets stuck in infinite loop building dependency reduced POM
> ------------------------------------------------------------------------
>                 Key: MSHADE-148
>                 URL:
>             Project: Maven 2.x Shade Plugin
>          Issue Type: Bug
>    Affects Versions: 2.1
>         Environment: OS X 10.7.5
>            Reporter: Rob Vesse
>         Attachments: dependency-reduced-pom.xml, pom.xml, shade-bug.txt
> I have encountered a bug whereby the shade plugin gets stuck in an infinite loop in the
step of creating a dependency reduced POM.
> I have attached a minimal POM that reproduces the issue and done some debugging on this.
 The problem seems to be caused by using both the jar and test-jar version of a dependency
(jena-fuseki in my example) while also including a jar dependency that is a transitive dependency
of the other dependencies (jena-arq in my example).   Removing either the jar/test-jar resolves
the problem and so does removing the other jar dependency.
> The problem appears to be that the plugin is getting stuck endlessly trying to produce
the dependency-reduced-pom.xml
> If I watch the file over time it is repeatedly deleted and rewritten, each time it is
written it gets larger.  When I manage to kill the process at a point where the file is non-empty
I can see that the plugin is endlessly adding the same set of <exclusions> to one of
the jena-fuseki dependencies.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message