[
https://jira.codehaus.org/browse/MDEP-322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=278192#comment-278192
]
Gili commented on MDEP-322:
---------------------------
Use-case: Library A depends on library B. Library A unpacks native code found
in library B and incorporates it into the artifact. Anyone depending on library
A should not pull down library B because library A already incorporates the
necessary binaries (furthermore, library A doesn't need all the binaries found
in library B). The idea here is to encapsulate A's dependencies from the
outside world.
Maven doesn't support transitive native dependencies in the same way it does
for Java:
http://stackoverflow.com/questions/4171222/maven-depending-on-inheriting-artifact-causes-build-error
This issue isn't specify to inheritance. If B uses classifiers and A specifies
different classifiers depending on the <profile> used, then C depending on A
does not see any properties defined in A's profile. Consequently, C sees that A
depends on B, but it has no idea what classifier to use. I can either declare
the classifier twice (once in A, once in C) or have A encapsulate B and have C
just depend on A.
> Transitive support for copy and unpack goals
> --------------------------------------------
>
> Key: MDEP-322
> URL: https://jira.codehaus.org/browse/MDEP-322
> Project: Maven 2.x Dependency Plugin
> Issue Type: Wish
> Components: copy, unpack
> Affects Versions: 2.3
> Reporter: Gili
> Assignee: Brian Fox
>
> I'd like to be able to copy or unpack dependencies transitively, just like
> copy-dependencies or unpack-dependencies, but without having to declare the
> dependency on the current project.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
