[ 
https://issues.apache.org/jira/browse/MANTTASKS-41?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Osipov closed MANTTASKS-41.
-----------------------------------
    Resolution: Auto Closed

This issue has been auto closed because it has been inactive for a long period 
of time. If you think this issue still applies, retest your problem with the 
most recent version of Maven and the affected component, reopen and post your 
results.

> type attribute of artifact:dependencies doesn't work for indirect dependencies
> ------------------------------------------------------------------------------
>
>                 Key: MANTTASKS-41
>                 URL: https://issues.apache.org/jira/browse/MANTTASKS-41
>             Project: Maven Ant Tasks
>          Issue Type: Sub-task
>          Components: dependencies task
>            Reporter: Tomislav Bodor
>         Attachments: build.xml, pom.xml
>
>
> It appears that the type filter doesn't work properly with indirect 
> dependencies. It doesn't look like an issue with the TypeArtifactFilter 
> itself, but somewhere deeper. However, it's related to this feature, so here 
> it is...
> The problem manifests with transitive dependencies that are of different 
> type, e.g. a war artefact depends on a jar library. Whatever the type in that 
> case (jar or war), the dependency list returned by artifact:dependencies is 
> empty.
> I've traced through it and here is some more information:
> DefaultArtifactCollector applies the filter using ResolutionNode.filterTrail. 
> This iterates over the (dependency) node trail and applies the specified 
> filter to each dependency in turn. If all dependencies are of the same type 
> and the type matches the one specified in the filter, no problems. However, 
> I've got a dependency that is a war archive and that in turn has some jar 
> dependencies. If type is set to jar, filter fails when testing the first 
> dependency in the trail - the war in this case and never gets to the jar. The 
> result is that whatever the value of the type attribute, the dependency list 
> always ends up empty for trails that contain dependencies of different types.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to