[ 
https://jira.codehaus.org/browse/MSHADE-148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tom White updated MSHADE-148:
-----------------------------

    Attachment: MSHADE-148.patch

I encountered the same problem, and in Maven 3.1.1 using exclusions didn't work 
any more (it did in 3.0.4). See https://github.com/kite-sdk/kite/pull/2

I've written a patch (attached) that takes the artifact type into consideration 
when matching dependencies for excludes. With this patch my build now works 
using Maven 3.0.4 and 3.1.1, and what's more I don't need to specify any 
exclusions manually in my project's POM.

Please consider this patch for inclusion.
                
> Shade Plugin gets stuck in infinite loop building dependency reduced POM
> ------------------------------------------------------------------------
>
>                 Key: MSHADE-148
>                 URL: https://jira.codehaus.org/browse/MSHADE-148
>             Project: Maven Shade Plugin
>          Issue Type: Bug
>    Affects Versions: 2.1
>         Environment: OS X 10.7.5
>            Reporter: Rob Vesse
>         Attachments: dependency-reduced-pom.xml, MSHADE-148.patch, 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: http://www.atlassian.com/software/jira

Reply via email to